This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
spec:reviews:html5 [2011/08/03 15:28] – [Official CSSWG Comments (DRAFT)] fantasai | spec:reviews:html5 [2011/08/03 15:37] – [Attribute value normalization is not backwards compatible] fantasai | ||
---|---|---|---|
Line 13: | Line 13: | ||
We've added '': | We've added '': | ||
- | ==== ::cue and coordination ==== | + | ==== WebVTT rendering, |
- | ... | + | < |
+ | intended to be moved to its own CSS module once an | ||
+ | editor is found to run with it." | ||
+ | | ||
+ | | ||
+ | | ||
+ | We need a general statement that they shouldn' | ||
+ | | ||
+ | | ||
+ | | ||
+ | in CSS, there' | ||
+ | needs to be defined somewhere in CSS but we need to work together | ||
+ | on it at some point in the future. | ||
+ | ACTION plinss: Write up selectors coordination issue wrt ::cue et al. | ||
==== Normative references to CSS editors' | ==== Normative references to CSS 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 135: | 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 === |