11362 2010-11-21 00:33:21 +0000 <style scoped="scoped"> fails validation unless <div> is added within parent 2015-08-23 07:07:43 +0000 1 1 1 Unclassified HTML Checker General unspecified Macintosh MacOS X RESOLVED FIXED http://www.lavacochesnely.es/ P2 normal --- 1 Rob.Simpson mike lavacochesmadrid www-validator-cvs oldest_to_newest 42668 0 Rob.Simpson 2010-11-21 00:33:21 +0000 The HTML 5 specifications indicate that <style scoped="scoped"> can be used in flow content. While this validates OK under a parent <div>, it fails under other elements that expect flow content. For example, when coding a "breadcrumb trail": <nav> <style scoped="scoped"> li { display: inline } </style> <ul> <li>...</li> </ul> </nav> The validator reports the following: XHTML element style not allowed as child of XHTML element nav in this context. (Suppressing further errors from this subtree.) <style scoped="scoped"> Contexts in which element style may be used: ... If the scoped attribute is present: where flow content is expected, but before any other flow content other than other style elements and inter-element whitespace. Content model for element nav: Flow content. If a <div> is added inside the parent <nav> then it validates OK: <nav> <div> <style scoped="scoped"> li { display: inline } </style> <ul> <li>...</li> </ul> </div> </nav> 42684 1 mike 2010-11-22 07:02:11 +0000 This is a known issue that has to do with the HTML5 schema used by the validation backend not being up to date with the spec. See bug 10348 also. I will try to get the schema updated soonish. 42705 2 Rob.Simpson 2010-11-22 19:19:18 +0000 Not sure what bug #10348 has to do with this one since scoped is a boolean attribute and the rule that "The values 'true' and 'false' are not allowed on boolean attributes"** dictates that all of that issue's use cases would be expected to be "Invalid", which in fact are currently the actual results (even for the one that says "Valid") which means the validation backend _is_ up to date for that issue. ** Quote (from http://www.HTML-5.com/tutorials/converting-to-html-5.html) (I just double-checked to make sure this is current information, and it comes from Section 2.5.2 of the Working Draft 19 October 2010.) >> Note that the HTML 5 specifications explicitly state that: >> >> The values "true" and "false" are not allowed on boolean attributes. >> >> This is because browsers that look at the coded value for boolean attributes >> would treat the string "false" as false while browsers that only look for the >> presence or absence of the attribute would treat that code as true, resulting >> in very inconsistent behavior. Thanks for looking at both issues. Maybe bug #10348 could be closed. 86459 3 mike 2013-04-22 03:13:55 +0000 Fixed. You can test at http://validator.w3.org/nu/