[Bug 13102] <style scoped> conflicts with top-placed <figcaption>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13102

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |FIXED

--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-18 22:53:27 UTC ---
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.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 18 August 2011 22:53:30 UTC