This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
spec:reviews:html5 [2011/08/03 15:21] – [Chapter 10 more clearly marked as informative] fantasai | spec:reviews:html5 [2014/12/09 15:48] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 5: | Line 5: | ||
===== Official CSSWG Comments (DRAFT) ===== | ===== Official CSSWG Comments (DRAFT) ===== | ||
- | * UI selectors - need to define / verify proper split of definition of UI selectors in CSS3-UI | + | ==== Pseudo-selectors |
- | | + | |
- | | + | It is our understanding that the CSSWG defines pseudo-class selectors in its modules, |
- | | + | |
- | | + | With regards to '' |
- | * ... to be provided | + | |
- | * case-insensitive attribute value matching; http:// | + | We've added '' |
- | * rendering depends on video { object-fit: contain; } | + | |
- | * for defining | + | ==== WebVTT rendering, ::cue, and coordination ==== |
+ | |||
+ | < | ||
+ | intended to be moved to its own CSS module once an | ||
+ | editor is found to run with it." | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | in CSS, there' | ||
+ | needs to be defined somewhere in CSS but we need to work together | ||
+ | on it at some point in the future. | ||
+ | | ||
+ | |||
+ | ==== Normative | ||
+ | |||
+ | fantasai: CSSWG handles editors' | ||
+ | not the official WG-endorsed copy | ||
+ | | ||
+ | < | ||
+ | < | ||
+ | | ||
+ | | ||
+ | they have something to update | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
==== Automatic height for transcluded elements (SEAMLESS attribute) ==== | ==== Automatic height for transcluded elements (SEAMLESS attribute) ==== | ||
Line 129: | Line 160: | ||
Chapter 10 on rendering seems to say that elements and attributes are matched against CSS selectors in a case-insensitive way, even if the document is in XML. (The chapter itself is not normative, but I assume it says that because there is corresponding normative text somewhere else.) That contradicts XML. It also breaks existing style sheets, e.g., user style sheets that rely on the fact that | Chapter 10 on rendering seems to say that elements and attributes are matched against CSS selectors in a case-insensitive way, even if the document is in XML. (The chapter itself is not normative, but I assume it says that because there is corresponding normative text somewhere else.) That contradicts XML. It also breaks existing style sheets, e.g., user style sheets that rely on the fact that | ||
- | body [color: green} | + | body {color: green} |
BODY {color: blue} | BODY {color: blue} | ||
makes XHTML documents green and HTML ones blue. | makes XHTML documents green and HTML ones blue. | ||
+ | |||
+ | **Anne notes** that this comment is incorrect, that the case-insensitivity only applies to attribute values and only for the rules listed in that section as UA style rules. | ||
=== Pseudo-namespaces in HTML === | === Pseudo-namespaces in HTML === |