20638 2013-01-10 19:16:06 +0000 Is scoped required if 'style' is not in 'head'? The wording is too vague. Validators raise errors for missing 'scoped', but here it is described as optional. 2013-04-12 23:18:55 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#the-style-element P3 normal Unsorted 1 contributor ian ian mike contributor oldest_to_newest 81202 0 contributor 2013-01-10 19:16:06 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html Multipage: http://www.whatwg.org/C#the-style-element Complete: http://www.whatwg.org/c#the-style-element Comment: Is scoped required if 'style' is not in 'head'? The wording is too vague. Validators raise errors for missing 'scoped', but here it is described as optional. Posted from: 84.183.87.178 User agent: Opera/9.80 (Windows NT 6.1; Win64; x64) Presto/2.12.388 Version/12.11 84094 1 ian 2013-03-07 23:17:30 +0000 I don't understand why it's vague. The spec very explicitly says "If the scoped attribute is present and the element has a parent element, then the style element must be the first node of flow content in its parent element other than inter-element whitespace, and the parent element's content model must not have a transparent component", and the element's categories only include "flow content" (which is what would allow it to be used outside of <head>) if the element has a "scoped" attribute. I can add a non-normative note, if that would help, but where should I add it such that it would be more visible than the above? 86105 2 ian 2013-04-12 23:16:21 +0000 I've tried to be more explicit, but I've no idea if it's enough. 86106 3 contributor 2013-04-12 23:18:55 +0000 Checked in as WHATWG revision r7825. Check-in comment: More elaboraton on <style scoped> requirements. http://html5.org/tools/web-apps-tracker?from=7824&to=7825