This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13102 - <style scoped> conflicts with top-placed <figcaption>
Summary: <style scoped> conflicts with top-placed <figcaption>
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-30 16:36 UTC by Oli Studholme
Modified: 2011-08-18 22:53 UTC (History)
7 users (show)

See Also:


Attachments

Description Oli Studholme 2011-06-30 16:36:08 UTC
If you want to use <figcaption> at the top of a <figure> its 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>.

Id 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>.
Comment 1 Tab Atkins Jr. 2011-06-30 16:46:56 UTC
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.)
Comment 2 Michael[tm] Smith 2011-08-04 05:36:11 UTC
mass-move component to LC1
Comment 3 Ian 'Hixie' Hickson 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.
Comment 4 contributor 2011-08-18 22:53:44 UTC
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