13102 2011-06-30 16:36:08 +0000 <style scoped> conflicts with top-placed <figcaption> 2011-08-18 22:53:44 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All RESOLVED FIXED P2 normal --- 1 w3.org ian ayg eoconnor ian jackalmage mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 50502 0 w3.org 2011-06-30 16:36:08 +0000 If you want to use <figcaption> at the top of a <figure> it’s currently not possible to use <style scoped> for that <figure>, as both elements should be the first child. I expected <style scoped> to be allowed before <figcaption>. I’d like to suggest the <figcaption> spec “Contexts in which this element can be used” text: As the first or last child of a figure element. be changed to something like: As the first or last child of a figure element, or the second child of a figure element with a style scoped element Current workaround is to move <style scoped> into a wrapper <div>. 50504 1 jackalmage 2011-06-30 16:46:56 +0000 Hmm, good point. Alternately, we could somehow define in <style> that it doesn't interfere with requirements like that. (Same thing, just different spec placement.) 54112 2 mike 2011-08-04 05:36:11 +0000 mass-move component to LC1 55448 3 ian 2011-08-18 22:53:27 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Partially Accepted Change Description: see diff below Rationale: Nothing in the spec actually required that the <style scoped> element come first, as far as I can tell. The only mention of the requirement was the non-normative "Contexts in which this element can be used" text, and it didn't say anything about having to be the first child, it just says it has to come before any other flow content. I've added a normative requirement to the effect to the spec. 55449 4 contributor 2011-08-18 22:53:44 +0000 Checked in as WHATWG revision r6513. Check-in comment: Actually require what the spec claimed to require. http://html5.org/tools/web-apps-tracker?from=6512&to=6513