You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<liclass="tocline2"><ahref="grammar.html#tokenizer-diffs" class="tocxref"><del>D.3</del><ins>G.3</ins> Comparison of tokenization in <del>CSS2</del><ins>CSS 2.1</ins> and CSS1</a>
32
+
<liclass="tocline2"><ahref="grammar.html#q4" class="tocxref"><del>This appendix is normative.</del><ins>G.4 Implementation note</ins></a>
32
33
</ul>
33
34
</div>
34
35
35
-
<P><del>This appendix is normative.</del>The grammar below defines the syntax of <del>CSS2.</del><ins>CSS 2.1.</ins> It is in some sense,
36
+
<P>The grammar below defines the syntax of <del>CSS2.</del><ins>CSS 2.1.</ins> It is in some sense,
36
37
however, a superset of <del>CSS2</del><ins>CSS 2.1</ins> as this specification imposes additional
37
38
semantic constraints not expressed in this grammar. A conforming UA
38
39
must also adhere to the <ahref="./syndata.html#syntax">
attribute selectors.</ins> Style sheets should be designed so that they work
495
495
even if the default values are not included in the document tree.
496
496
497
-
<p><del>Example(s): For example, consider an element EXAMPLE with an attribute "notation" that has</del><ins>More precisely,</ins> a <del>default value</del><ins>UA is</ins><em><ins>not</ins></em><ins>required to read an "external
498
-
subset"</ins> of <del>"decimal".</del>the DTD <del>fragment might be <!ATTLIST EXAMPLE notation (decimal,octal) "decimal"> If the style sheet contains the rules EXAMPLE[notation=decimal] {</del><ins>but</ins><em><ins>is</ins></em><ins>required to look for default
499
-
attribute values in the document's "internal subset." (See</ins><ahref="refs.html#ref-XML10" rel="biblioentry" class="noxref"><spanclass="normref"><ins>[XML10]</ins></span></a>
500
-
<ins>for definitions of these subsets.)</ins>
501
-
502
-
<p><ins>A UA that recognizes an XML namespace</ins><ahref="refs.html#ref-XMLNAMESPACES" rel="biblioentry" class="noxref"><spanclass="informref"><ins>[XMLNAMESPACES]</ins></span></a><ins>is not
503
-
required to use its knowledge of that namespace to treat default
497
+
<p><del>Example(s): For example, consider an element EXAMPLE with</del><ins>More precisely, a UA may, but is</ins><em><ins>not</ins></em><ins>required to, read</ins> an <ins>"external
498
+
subset" of the DTD but</ins><em><ins>is</ins></em><ins>required to look for default</ins>
499
+
attribute <del>"notation" that has</del><ins>values in the document's "internal subset." (See</ins><ahref="refs.html#ref-XML10" rel="biblioentry" class="noxref"><spanclass="normref"><ins>[XML10]</ins></span></a>
500
+
<ins>for definitions of these subsets.)
501
+
Depending on the UA,</ins> a default <ins>attribute</ins> value <del>of</del><ins>defined in the external
502
+
subset of the DTD might or might not appear in the document tree.</ins>
503
+
504
+
<p><ins>A UA that recognizes an XML namespace</ins><ahref="refs.html#ref-XMLNAMESPACES" rel="biblioentry" class="noxref"><spanclass="informref"><ins>[XMLNAMESPACES]</ins></span></a><ins>may, but is not
505
+
required to, use its knowledge of that namespace to treat default
504
506
attribute values as if they were present in the document. (E.g., an
505
507
XHTML UA is not required to use its built-in knowledge of the XHTML
<divclass="note"><p><em><strong><del>5.9 ID selectors Document languages</del><ins>Note:</ins></strong><ins>If an element has
624
-
multiple class attributes, their values must be concatenated with
625
+
<divclass="note"><p><em><strong><del>5.9 ID selectors Document languages may contain attributes that are declared to</del><ins>Note:</ins></strong><ins>If an element has
626
+
multiple class attributes, their values must</ins> be <del>of type</del><ins>concatenated with
625
627
spaces between the values before searching for the class. As of this
626
628
time the working group is not aware of any manner in which this
627
629
situation can be reached, however, so this behavior is explicitly
0 commit comments