[css3-conditional] Hurp durp, how about I only fix the ids that actually need fixing?

Fri, 31 Aug 2012 11:57:12 -0700

author
Tab Atkins Jr. <jackalmage@gmail.com>
date
Fri, 31 Aug 2012 11:57:12 -0700
changeset 6617
349a7ea1e24c
parent 6616
d551cb44e735
child 6618
7aa15649c232

[css3-conditional] Hurp durp, how about I only fix the ids that actually need fixing?

css3-conditional/Overview.html file | annotate | diff | comparison | revisions
css3-conditional/Overview.src.html file | annotate | diff | comparison | revisions
     1.1 --- a/css3-conditional/Overview.html	Fri Aug 31 11:53:59 2012 -0700
     1.2 +++ b/css3-conditional/Overview.html	Fri Aug 31 11:57:12 2012 -0700
     1.3 @@ -105,8 +105,8 @@
     1.4     <a href="#CSS1" rel=biblioentry>[CSS1]<!--{{CSS1}}--></a>. The main
     1.5     extensions compared to level 2 are allowing nesting of certain at-rules
     1.6     inside ‘<code class=css>@media</code>’, the addition of the ‘<a
     1.7 -   href="#&#34;dfn-support&#34;"><code class=css>@supports</code></a>’ and
     1.8 -   ‘<code class=css>@document</code>’ rules for conditional processing.
     1.9 +   href="#dfn-support"><code class=css>@supports</code></a>’ and ‘<code
    1.10 +   class=css>@document</code>’ rules for conditional processing.
    1.11  
    1.12    <h2 class="no-num no-toc" id=status>Status of this document</h2>
    1.13    <!--begin-status-->
    1.14 @@ -158,85 +158,84 @@
    1.15      be removed to advance the other features in this specification to
    1.16      Proposed Recommendation.
    1.17  
    1.18 -   <li>The ‘<a href="#&#34;dfn-support&#34;"><code
    1.19 -    class=css>@supports</code></a>’ rule is at risk; if interoperable
    1.20 -    implementations are not found, it may be removed to advance the other
    1.21 -    features in this specification to Proposed Recommendation.
    1.22 +   <li>The ‘<a href="#dfn-support"><code class=css>@supports</code></a>’
    1.23 +    rule is at risk; if interoperable implementations are not found, it may
    1.24 +    be removed to advance the other features in this specification to
    1.25 +    Proposed Recommendation.
    1.26  
    1.27     <li>The ‘<code class=css>@document</code>’ rule is at risk; if
    1.28      interoperable implementations are not found, it may be removed to advance
    1.29      the other features in this specification to Proposed Recommendation.
    1.30    </ul>
    1.31  
    1.32 -  <h2 class="no-num no-toc" id="&#34;contents&#34;">Table of contents</h2>
    1.33 +  <h2 class="no-num no-toc" id=contents>Table of contents</h2>
    1.34    <!--begin-toc-->
    1.35  
    1.36    <ul class=toc>
    1.37 -   <li><a href="#&#34;introduction&#34;"><span class=secno>1.
    1.38 -    </span>Introduction</a>
    1.39 +   <li><a href="#introduction"><span class=secno>1. </span>Introduction</a>
    1.40      <ul class=toc>
    1.41 -     <li><a href="#&#34;context&#34;"><span class=secno>1.1.
    1.42 -      </span>Background</a>
    1.43 +     <li><a href="#context"><span class=secno>1.1. </span>Background</a>
    1.44  
    1.45 -     <li><a href="#&#34;placement&#34;"><span class=secno>1.2. </span>Module
    1.46 +     <li><a href="#placement"><span class=secno>1.2. </span>Module
    1.47        Interactions</a>
    1.48  
    1.49 -     <li><a href="#&#34;conventions&#34;"><span class=secno>1.3.
    1.50 -      </span>Document Conventions</a>
    1.51 +     <li><a href="#conventions"><span class=secno>1.3. </span>Document
    1.52 +      Conventions</a>
    1.53      </ul>
    1.54  
    1.55 -   <li><a href="#&#34;processing&#34;"><span class=secno>2. </span>Processing
    1.56 -    of conditional group rules</a>
    1.57 -
    1.58 -   <li><a href="#&#34;contents-of&#34;"><span class=secno>3. </span>Contents
    1.59 -    of conditional group rules</a>
    1.60 -
    1.61 -   <li><a href="#&#34;use&#34;"><span class=secno>4. </span>Placement of
    1.62 +   <li><a href="#processing"><span class=secno>2. </span>Processing of
    1.63      conditional group rules</a>
    1.64  
    1.65 -   <li><a href="#&#34;at-media&#34;"><span class=secno>5.
    1.66 -    </span>Media-specific style sheets: the ‘<code
    1.67 -    class=css>@media</code>’ rule</a>
    1.68 +   <li><a href="#contents-of"><span class=secno>3. </span>Contents of
    1.69 +    conditional group rules</a>
    1.70  
    1.71 -   <li><a href="#&#34;at-supports&#34;"><span class=secno>6. </span>Feature
    1.72 -    queries: the ‘<code class=css>@supports</code>’ rule</a>
    1.73 +   <li><a href="#use"><span class=secno>4. </span>Placement of conditional
    1.74 +    group rules</a>
    1.75 +
    1.76 +   <li><a href="#at-media"><span class=secno>5. </span>Media-specific style
    1.77 +    sheets: the ‘<code class=css>@media</code>’ rule</a>
    1.78 +
    1.79 +   <li><a href="#at-supports"><span class=secno>6. </span>Feature queries:
    1.80 +    the ‘<code class=css>@supports</code>’ rule</a>
    1.81      <ul class=toc>
    1.82 -     <li><a href="#&#34;support-definition&#34;"><span class=secno>6.1.
    1.83 +     <li><a href="#support-definition"><span class=secno>6.1.
    1.84        </span>Definition of support</a>
    1.85  
    1.86 -     <li><a href="#&#34;partial-implementations&#34;"><span class=secno>6.2.
    1.87 +     <li><a href="#partial-implementations"><span class=secno>6.2.
    1.88        </span>Partial implementations</a>
    1.89      </ul>
    1.90  
    1.91 -   <li><a href="#&#34;at-document&#34;"><span class=secno>7. </span>Document
    1.92 -    queries: the ‘<code class=css>@document</code>’ rule</a>
    1.93 +   <li><a href="#at-document"><span class=secno>7. </span>Document queries:
    1.94 +    the ‘<code class=css>@document</code>’ rule</a>
    1.95  
    1.96 -   <li><a href="#&#34;apis&#34;"><span class=secno>8. </span>APIs</a>
    1.97 +   <li><a href="#apis"><span class=secno>8. </span>APIs</a>
    1.98      <ul class=toc>
    1.99 -     <li><a href="#&#34;the-csssupportsrule-interface&#34;"><span
   1.100 -      class=secno>8.1. </span> The <code>CSSSupportsRule</code> interface</a>
   1.101 +     <li><a href="#extentions-to-cssrule-interface"><span class=secno>8.1.
   1.102 +      </span> Extensions to the <code>CSSRule</code> interface</a>
   1.103  
   1.104 -     <li><a href="#&#34;window-api&#34;"><span class=secno>8.2.
   1.105 -      </span>supportsCSS() function</a>
   1.106 +     <li><a href="#the-csssupportsrule-interface"><span class=secno>8.2.
   1.107 +      </span> The <code>CSSSupportsRule</code> interface</a>
   1.108 +
   1.109 +     <li><a href="#window-api"><span class=secno>8.3. </span>supportsCSS()
   1.110 +      function</a>
   1.111      </ul>
   1.112  
   1.113 -   <li><a href="#&#34;conformance&#34;"><span class=secno>9.
   1.114 -    </span>Conformance</a>
   1.115 +   <li><a href="#conformance"><span class=secno>9. </span>Conformance</a>
   1.116      <ul class=toc>
   1.117 -     <li><a href="#&#34;base-modules&#34;"><span class=secno>9.1. </span>Base
   1.118 +     <li><a href="#base-modules"><span class=secno>9.1. </span>Base
   1.119        Modules</a>
   1.120  
   1.121 -     <li><a href="#&#34;conformance-classes&#34;"><span class=secno>9.2.
   1.122 +     <li><a href="#conformance-classes"><span class=secno>9.2.
   1.123        </span>Conformance Classes</a>
   1.124  
   1.125 -     <li><a href="#&#34;partial&#34;"><span class=secno>9.3. </span> Partial
   1.126 +     <li><a href="#partial"><span class=secno>9.3. </span> Partial
   1.127        Implementations</a>
   1.128  
   1.129 -     <li><a href="#&#34;experimental&#34;"><span class=secno>9.4.
   1.130 -      </span>Experimental Implementations</a>
   1.131 +     <li><a href="#experimental"><span class=secno>9.4. </span>Experimental
   1.132 +      Implementations</a>
   1.133  
   1.134 -     <li><a href="#&#34;cr-exit-criteria&#34;"><span class=secno>9.5.
   1.135 -      </span>CR Exit Criteria</a>
   1.136 +     <li><a href="#cr-exit-criteria"><span class=secno>9.5. </span>CR Exit
   1.137 +      Criteria</a>
   1.138      </ul>
   1.139  
   1.140     <li class=no-num><a href="#grammar">Grammar</a>
   1.141 @@ -245,20 +244,19 @@
   1.142  
   1.143     <li class=no-num><a href="#references">References</a>
   1.144      <ul class=toc>
   1.145 -     <li class=no-num><a href="#&#34;normative-references&#34;">Normative
   1.146 +     <li class=no-num><a href="#normative-references">Normative
   1.147        references</a>
   1.148  
   1.149 -     <li class=no-num><a href="#&#34;other-references&#34;">Other
   1.150 -      references</a>
   1.151 +     <li class=no-num><a href="#other-references">Other references</a>
   1.152      </ul>
   1.153  
   1.154 -   <li class=no-num><a href="#&#34;index&#34;">Index</a>
   1.155 +   <li class=no-num><a href="#index">Index</a>
   1.156    </ul>
   1.157    <!--end-toc-->
   1.158  
   1.159 -  <h2 id="&#34;introduction&#34;"><span class=secno>1. </span>Introduction</h2>
   1.160 +  <h2 id=introduction><span class=secno>1. </span>Introduction</h2>
   1.161  
   1.162 -  <h3 id="&#34;context&#34;"><span class=secno>1.1. </span>Background</h3>
   1.163 +  <h3 id=context><span class=secno>1.1. </span>Background</h3>
   1.164  
   1.165    <p><em>This section is not normative.</em>
   1.166  
   1.167 @@ -280,26 +278,24 @@
   1.168     single style sheet.
   1.169  
   1.170    <p>This specification also defines additional types of conditional group
   1.171 -   rules, ‘<a href="#&#34;dfn-support&#34;"><code
   1.172 -   class=css>@supports</code></a>’ and ‘<code
   1.173 -   class=css>@document</code>’, to address author and user requirements.
   1.174 +   rules, ‘<a href="#dfn-support"><code class=css>@supports</code></a>’
   1.175 +   and ‘<code class=css>@document</code>’, to address author and user
   1.176 +   requirements.
   1.177  
   1.178 -  <p>The ‘<a href="#&#34;dfn-support&#34;"><code
   1.179 -   class=css>@supports</code></a>’ rule allows CSS to be conditioned on
   1.180 -   implementation support for CSS properties and values. This rule makes it
   1.181 -   much easier for authors to use new CSS features and provide good fallback
   1.182 -   for implementations that do not support those features. This is
   1.183 -   particularly important for CSS features that provide new layout
   1.184 -   mechanisms, and for other cases where a set of related styles needs to be
   1.185 -   conditioned on property support.
   1.186 +  <p>The ‘<a href="#dfn-support"><code class=css>@supports</code></a>’
   1.187 +   rule allows CSS to be conditioned on implementation support for CSS
   1.188 +   properties and values. This rule makes it much easier for authors to use
   1.189 +   new CSS features and provide good fallback for implementations that do not
   1.190 +   support those features. This is particularly important for CSS features
   1.191 +   that provide new layout mechanisms, and for other cases where a set of
   1.192 +   related styles needs to be conditioned on property support.
   1.193  
   1.194    <p>The ‘<code class=css>@document</code>’ rule allows CSS to be
   1.195     conditioned on the page to which the style sheet is being applied. This
   1.196     allows users to apply styles to a particular page or group of pages, which
   1.197     greatly increases the power of user style sheets.
   1.198  
   1.199 -  <h3 id="&#34;placement&#34;"><span class=secno>1.2. </span>Module
   1.200 -   Interactions</h3>
   1.201 +  <h3 id=placement><span class=secno>1.2. </span>Module Interactions</h3>
   1.202  
   1.203    <p>This module replaces and extends the ‘<code class=css>@media</code>’
   1.204     rule feature defined in <a href="#CSS21"
   1.205 @@ -316,8 +312,7 @@
   1.206     of this one. If this module advances faster, then the dependency will be
   1.207     reversed.
   1.208  
   1.209 -  <h3 id="&#34;conventions&#34;"><span class=secno>1.3. </span>Document
   1.210 -   Conventions</h3>
   1.211 +  <h3 id=conventions><span class=secno>1.3. </span>Document Conventions</h3>
   1.212  
   1.213    <p>Conformance requirements are expressed with a combination of descriptive
   1.214     assertions and RFC 2119 terminology. The key words “MUST”, “MUST
   1.215 @@ -344,8 +339,8 @@
   1.216  
   1.217    <p class=note>Note, this is an informative note.
   1.218  
   1.219 -  <h2 id="&#34;processing&#34;"><span class=secno>2. </span>Processing of
   1.220 -   conditional group rules</h2>
   1.221 +  <h2 id=processing><span class=secno>2. </span>Processing of conditional
   1.222 +   group rules</h2>
   1.223  
   1.224    <p>This specification defines some CSS @-rules, called <dfn
   1.225     id=conditional-group-rules>conditional group rules</dfn>, that associate a
   1.226 @@ -412,8 +407,8 @@
   1.227     href="#CSS3-ANIMATIONS"
   1.228     rel=biblioentry>[CSS3-ANIMATIONS]<!--{{!CSS3-ANIMATIONS}}--></a>).
   1.229  
   1.230 -  <h2 id="&#34;contents-of&#34;"><span class=secno>3. </span>Contents of
   1.231 -   conditional group rules</h2>
   1.232 +  <h2 id=contents-of><span class=secno>3. </span>Contents of conditional
   1.233 +   group rules</h2>
   1.234  
   1.235    <p class=issue>There is also likely demand for using these conditions with
   1.236     ‘<code class=css>@import</code>’. We should see if we can come up with
   1.237 @@ -472,8 +467,7 @@
   1.238     (Rule sets, declaration blocks, and selectors)</a> of <a href="#CSS21"
   1.239     rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>.
   1.240  
   1.241 -  <h2 id="&#34;use&#34;"><span class=secno>4. </span>Placement of conditional
   1.242 -   group rules</h2>
   1.243 +  <h2 id=use><span class=secno>4. </span>Placement of conditional group rules</h2>
   1.244  
   1.245    <p>Conditional group rules are allowed at the top-level of a style sheet,
   1.246     and inside other conditional group rules. CSS processors
   1.247 @@ -487,8 +481,8 @@
   1.248     not</strong> place such rules after a conditional group rules, and CSS
   1.249     processors <strong>must</strong> ignore such rules.
   1.250  
   1.251 -  <h2 id="&#34;at-media&#34;"><span class=secno>5. </span>Media-specific
   1.252 -   style sheets: the ‘<code class=css>@media</code>’ rule</h2>
   1.253 +  <h2 id=at-media><span class=secno>5. </span>Media-specific style sheets:
   1.254 +   the ‘<code class=css>@media</code>’ rule</h2>
   1.255  
   1.256    <p>The <dfn id=media-rule>‘<code class=css>@media</code>’ rule</dfn> is
   1.257     a conditional group rule whose condition is a media query. It consists of
   1.258 @@ -528,9 +522,8 @@
   1.259     href="http://www.w3.org/TR/CSS21/grammar.html">Grammar of CSS 2.1</a> (<a
   1.260     href="#CSS21" rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>, Appendix G).
   1.261  
   1.262 -  <h2 id="&#34;at-supports&#34;"><span class=secno>6. </span>Feature queries:
   1.263 -   the ‘<a href="#&#34;dfn-support&#34;"><code
   1.264 -   class=css>@supports</code></a>’ rule</h2>
   1.265 +  <h2 id=at-supports><span class=secno>6. </span>Feature queries: the ‘<a
   1.266 +   href="#dfn-support"><code class=css>@supports</code></a>’ rule</h2>
   1.267  
   1.268    <p>The <dfn id=supports-rule>‘<code class=css>@supports</code>’
   1.269     rule</dfn> is a conditional group rule whose condition tests whether the
   1.270 @@ -542,10 +535,10 @@
   1.271     tied to the support for certain features, as is the case for use of new
   1.272     layout system features.
   1.273  
   1.274 -  <p>The syntax of the condition in the ‘<a
   1.275 -   href="#&#34;dfn-support&#34;"><code class=css>@supports</code></a>’ rule
   1.276 -   is slightly more complicated than for the other conditional group rules
   1.277 -   (though has some similarities to media queries) since:
   1.278 +  <p>The syntax of the condition in the ‘<a href="#dfn-support"><code
   1.279 +   class=css>@supports</code></a>’ rule is slightly more complicated than
   1.280 +   for the other conditional group rules (though has some similarities to
   1.281 +   media queries) since:
   1.282  
   1.283    <ul>
   1.284     <li>negation is needed so that the new-feature styles and the fallback
   1.285 @@ -560,7 +553,7 @@
   1.286      alternatives are vendor-prefixed properties or values
   1.287    </ul>
   1.288  
   1.289 -  <p>Therefore, the syntax of the ‘<a href="#&#34;dfn-support&#34;"><code
   1.290 +  <p>Therefore, the syntax of the ‘<a href="#dfn-support"><code
   1.291     class=css>@supports</code></a>’ rule allows testing for property:value
   1.292     pairs, and arbitrary conjunctions (and), disjunctions (or), and negations
   1.293     (not) of them.
   1.294 @@ -615,22 +608,22 @@
   1.295     (Tokenization)</a> of <a href="#CSS21"
   1.296     rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>.
   1.297  
   1.298 -  <p>Any ‘<a href="#&#34;dfn-support&#34;"><code
   1.299 -   class=css>@supports</code></a>’ rule that does not parse according to
   1.300 -   the grammar above is invalid. Style sheets <strong>must not</strong> use
   1.301 -   such a rule and processors <strong>must</strong> ignore such a rule.
   1.302 +  <p>Any ‘<a href="#dfn-support"><code class=css>@supports</code></a>’
   1.303 +   rule that does not parse according to the grammar above is invalid. Style
   1.304 +   sheets <strong>must not</strong> use such a rule and processors
   1.305 +   <strong>must</strong> ignore such a rule.
   1.306  
   1.307    <p class=note>Note that this means that declarations that meet the
   1.308     forward-compatible syntax for declarations are permitted (and support for
   1.309 -   them is then tested by the ‘<a href="#&#34;dfn-support&#34;"><code
   1.310 +   them is then tested by the ‘<a href="#dfn-support"><code
   1.311     class=css>@supports</code></a>’ rule), but declarations that do not meet
   1.312     the forward-compatible syntax for declarations cause the entire ‘<a
   1.313 -   href="#&#34;dfn-support&#34;"><code class=css>@supports</code></a>’ rule
   1.314 -   to be ignored.
   1.315 +   href="#dfn-support"><code class=css>@supports</code></a>’ rule to be
   1.316 +   ignored.
   1.317  
   1.318    <p class=issue>Is any further allowance for forward-compatible parsing
   1.319     needed, for example, to allow additional features (such as, say, selector
   1.320 -   tests) to be added to the ‘<a href="#&#34;dfn-support&#34;"><code
   1.321 +   tests) to be added to the ‘<a href="#dfn-support"><code
   1.322     class=css>@supports</code></a>’ rule? Or are these forward-compatible
   1.323     parsing rules the best solution for such future expansion anyway?
   1.324  
   1.325 @@ -673,7 +666,7 @@
   1.326      href="#support-definition">supports</a> the declaration.
   1.327    </dl>
   1.328  
   1.329 -  <p>The condition of the ‘<a href="#&#34;dfn-support&#34;"><code
   1.330 +  <p>The condition of the ‘<a href="#dfn-support"><code
   1.331     class=css>@supports</code></a>’ rule is the result of the <a
   1.332     href="#supportscondition"><code>supports_condition</code></a> term that is
   1.333     a child of the <a href="#supportsrule"><code>supports_rule</code></a>
   1.334 @@ -688,16 +681,16 @@
   1.335    #article { background: white; color: black; }
   1.336  }</pre>
   1.337  
   1.338 -   <p>applies the rules inside the ‘<a href="#&#34;dfn-support&#34;"><code
   1.339 +   <p>applies the rules inside the ‘<a href="#dfn-support"><code
   1.340      class=css>@supports</code></a>’ rule only when ‘<code
   1.341      class=css>display: flexbox</code>’ is supported.
   1.342    </div>
   1.343  
   1.344    <div class=example>
   1.345     <p>The following example shows an additional ‘<a
   1.346 -    href="#&#34;dfn-support&#34;"><code class=css>@supports</code></a>’
   1.347 -    rule that can be used to provide an alternative for when ‘<code
   1.348 -    class=css>display: flexbox</code>’ is not supported:
   1.349 +    href="#dfn-support"><code class=css>@supports</code></a>’ rule that can
   1.350 +    be used to provide an alternative for when ‘<code class=css>display:
   1.351 +    flexbox</code>’ is not supported:
   1.352  
   1.353     <pre>@supports not ( display: flexbox ) {
   1.354    body { width: 100%; height: 100%; background: white; color: black; }
   1.355 @@ -799,16 +792,15 @@
   1.356  
   1.357    <p class=issue>Add an example involving <code>!important</code>.
   1.358  
   1.359 -  <h3 id="&#34;support-definition&#34;"><span class=secno>6.1.
   1.360 -   </span>Definition of support</h3>
   1.361 +  <h3 id=support-definition><span class=secno>6.1. </span>Definition of
   1.362 +   support</h3>
   1.363  
   1.364 -  <p>A CSS processor is considered to <dfn
   1.365 -   id="&#34;dfn-support&#34;">support</dfn> a declaration (consisting of a
   1.366 -   property and value) if it implements the given value of the given
   1.367 -   property.
   1.368 +  <p>A CSS processor is considered to <dfn id=dfn-support>support</dfn> a
   1.369 +   declaration (consisting of a property and value) if it implements the
   1.370 +   given value of the given property.
   1.371  
   1.372 -  <h3 id="&#34;partial-implementations&#34;"><span class=secno>6.2.
   1.373 -   </span>Partial implementations</h3>
   1.374 +  <h3 id=partial-implementations><span class=secno>6.2. </span>Partial
   1.375 +   implementations</h3>
   1.376  
   1.377    <p>For forward-compatibility, <a
   1.378     href="http://www.w3.org/TR/CSS21/syndata.html#declaration">section 4.1.8
   1.379 @@ -828,16 +820,16 @@
   1.380     containing such a value. This allows authors to use fallback (either in
   1.381     the <a href="#CSS1" rel=biblioentry>[CSS1]<!--{{CSS1}}--></a> sense of
   1.382     declarations that are overridden by later declarations or with the new
   1.383 -   capabilities provided by the ‘<a href="#&#34;dfn-support&#34;"><code
   1.384 +   capabilities provided by the ‘<a href="#dfn-support"><code
   1.385     class=css>@supports</code></a>’ rule in this specification) that works
   1.386     correctly for the features implemented. This applies especially to
   1.387     compound values; implementations must implement all parts of the value in
   1.388     order to consider the declaration supported, either inside a ruleset or in
   1.389 -   the declaration condition of an ‘<a href="#&#34;dfn-support&#34;"><code
   1.390 +   the declaration condition of an ‘<a href="#dfn-support"><code
   1.391     class=css>@supports</code></a>’ rule.
   1.392  
   1.393 -  <h2 id="&#34;at-document&#34;"><span class=secno>7. </span>Document
   1.394 -   queries: the ‘<code class=css>@document</code>’ rule</h2>
   1.395 +  <h2 id=at-document><span class=secno>7. </span>Document queries: the
   1.396 +   ‘<code class=css>@document</code>’ rule</h2>
   1.397  
   1.398    <p>The <dfn id=document-rule>‘<code class=css>@document</code>’
   1.399     rule</dfn> is a conditional group rule whose condition depends on the <a
   1.400 @@ -851,13 +843,12 @@
   1.401     should this specification remain neutral on the topic, since there are
   1.402     valid uses in author style sheets?
   1.403  
   1.404 -  <p id="&#34;url-of-doc&#34;">The <dfn
   1.405 -   id=url-of-the-document-being-styled>URL of the document being styled</dfn>
   1.406 -   is the URI at which the document is located, excluding any fragment
   1.407 -   identifiers. (This means, for example, that HTTP redirects have been
   1.408 -   followed.) If the styles are being applied inside a complete document
   1.409 -   embedded into the presentation of another (e.g., <a href="#HTML5"
   1.410 -   rel=biblioentry>[HTML5]<!--{{HTML5}}--></a>'s <code
   1.411 +  <p id=url-of-doc>The <dfn id=url-of-the-document-being-styled>URL of the
   1.412 +   document being styled</dfn> is the URI at which the document is located,
   1.413 +   excluding any fragment identifiers. (This means, for example, that HTTP
   1.414 +   redirects have been followed.) If the styles are being applied inside a
   1.415 +   complete document embedded into the presentation of another (e.g., <a
   1.416 +   href="#HTML5" rel=biblioentry>[HTML5]<!--{{HTML5}}--></a>'s <code
   1.417     class=html>iframe</code>, <code class=html>object</code>, or <code
   1.418     class=html>img</code> elements), the relevant URI is that of the frame,
   1.419     not of its container. However, if content from other documents is mixed in
   1.420 @@ -894,17 +885,17 @@
   1.421     are permitted:
   1.422  
   1.423    <dl>
   1.424 -   <dt><dfn id="&#34;url-exact&#34;"
   1.425 +   <dt><dfn id=url-exact
   1.426      title="url()|URL matching functions::exact">&lt;url&gt;</dfn>
   1.427  
   1.428     <dd>
   1.429 -    <p>The ‘<a href="#&#34;url-exact&#34;"><code
   1.430 -     class=css>url()</code></a>’ function is the <dfn
   1.431 -     id=exact-url-matching-function>exact url matching function</dfn>. It
   1.432 -     evaluates to true whenever the <a href="#url-of-doc">URL of the document
   1.433 -     being styled</a> is exactly the URL given.
   1.434 +    <p>The ‘<a href="#url-exact"><code class=css>url()</code></a>’
   1.435 +     function is the <dfn id=exact-url-matching-function>exact url matching
   1.436 +     function</dfn>. It evaluates to true whenever the <a
   1.437 +     href="#url-of-doc">URL of the document being styled</a> is exactly the
   1.438 +     URL given.
   1.439  
   1.440 -    <p class=Note>The ‘<a href="#&#34;url-exact&#34;"><code
   1.441 +    <p class=Note>The ‘<a href="#url-exact"><code
   1.442       class=css>url()</code></a>’ function, since it is a core syntax
   1.443       element in CSS, is allowed (subject to different character limitations
   1.444       and thus escaping requirements) to contain an unquoted value (in
   1.445 @@ -922,11 +913,11 @@
   1.446        <code>http://www.w3.org/Style/CSS/</code>, but not on any other pages.
   1.447      </div>
   1.448  
   1.449 -   <dt><dfn id="&#34;url-prefix&#34;"
   1.450 +   <dt><dfn id=url-prefix
   1.451      title="url-prefix()|URL matching functions::prefix">url-prefix(&lt;string&gt;)</dfn>
   1.452  
   1.453     <dd>
   1.454 -    <p>The ‘<a href="#&#34;url-prefix&#34;"><code
   1.455 +    <p>The ‘<a href="#url-prefix"><code
   1.456       class=css>url-prefix()</code></a>’ function is the <dfn
   1.457       id=url-prefix-matching-function>url prefix matching function</dfn>. It
   1.458       evaluates to true whenever the <a href="#url-of-doc">URL of the document
   1.459 @@ -948,21 +939,21 @@
   1.460        <code>http://www.example.com/Style/CSS/</code>.
   1.461      </div>
   1.462  
   1.463 -   <dt><dfn id="&#34;url-domain&#34;"
   1.464 +   <dt><dfn id=url-domain
   1.465      title="domain()|URL matching functions::domain">domain(&lt;string&gt;)</dfn>
   1.466  
   1.467     <dd>
   1.468 -    <p>The ‘<a href="#&#34;url-domain&#34;"><code
   1.469 -     class=css>domain()</code></a>’ function is the <dfn
   1.470 -     id=domain-matching-function>domain matching function</dfn>. It evaluates
   1.471 -     to true whenever the <a href="#url-of-doc">URL of the document being
   1.472 -     styled</a> has a host subcomponent (as defined in <a href="#URI"
   1.473 +    <p>The ‘<a href="#url-domain"><code class=css>domain()</code></a>’
   1.474 +     function is the <dfn id=domain-matching-function>domain matching
   1.475 +     function</dfn>. It evaluates to true whenever the <a
   1.476 +     href="#url-of-doc">URL of the document being styled</a> has a host
   1.477 +     subcomponent (as defined in <a href="#URI"
   1.478       rel=biblioentry>[URI]<!--{{!URI}}--></a>) and that host subcomponent is
   1.479 -     exactly the argument to the ‘<a href="#&#34;url-domain&#34;"><code
   1.480 +     exactly the argument to the ‘<a href="#url-domain"><code
   1.481       class=css>domain()</code></a>’ function or a final substring of the
   1.482       host component is a period (U+002E) immediately followed by the argument
   1.483 -     to the ‘<a href="#&#34;url-domain&#34;"><code
   1.484 -     class=css>domain()</code></a>’ function.
   1.485 +     to the ‘<a href="#url-domain"><code class=css>domain()</code></a>’
   1.486 +     function.
   1.487  
   1.488      <div class=example>
   1.489       <p>For example, this rule:
   1.490 @@ -978,7 +969,7 @@
   1.491        not affect the page <code>http://www.example.com/Style/CSS/</code>.
   1.492      </div>
   1.493  
   1.494 -   <dt><dfn id="&#34;url-regexp&#34;"
   1.495 +   <dt><dfn id=url-regexp
   1.496      title="regexp()|URL matching functions::regular expression">regexp(&lt;string&gt;)</dfn>
   1.497  
   1.498     <dd>
   1.499 @@ -989,11 +980,11 @@
   1.500       15.10.1). However, failing to do so is not a CSS syntax error and does
   1.501       not trigger any error handling for CSS syntax errors.
   1.502  
   1.503 -    <p>The ‘<a href="#&#34;url-regexp&#34;"><code
   1.504 -     class=css>regexp()</code></a>’ function evaluates to true whenever the
   1.505 -     string argument compiled as a JavaScript regular expression with the
   1.506 -     <code>global</code>, <code>ignoreCase</code> and <code>multiline</code>
   1.507 -     flags <em>disabled</em> (see <a href="#ECMA-262-5.1"
   1.508 +    <p>The ‘<a href="#url-regexp"><code class=css>regexp()</code></a>’
   1.509 +     function evaluates to true whenever the string argument compiled as a
   1.510 +     JavaScript regular expression with the <code>global</code>,
   1.511 +     <code>ignoreCase</code> and <code>multiline</code> flags
   1.512 +     <em>disabled</em> (see <a href="#ECMA-262-5.1"
   1.513       rel=biblioentry>[ECMA-262-5.1]<!--{{!ECMA-262-5.1}}--></a>, sections
   1.514       15.10.7.2 through 15.10.7.4) compiles successfully and the resulting
   1.515       regular expression matches the entirety of the <a href="#url-of-doc">URL
   1.516 @@ -1032,8 +1023,9 @@
   1.517     expansion anyway?</span>
   1.518  
   1.519    <div class=issue>This syntax doesn't offer any ability to do negations,
   1.520 -   which has been requested in Mozilla bug 349813. Use cases that people have
   1.521 -   wanted negations for include:
   1.522 +   which has been requested in <a
   1.523 +   href="https://bugzilla.mozilla.org/show_bug.cgi?id=349813">Mozilla bug
   1.524 +   349813</a>. Use cases that people have wanted negations for include:
   1.525     <ul>
   1.526      <li>User style sheets that want a particular rule in general, but know
   1.527       that that rule does more harm than good on specific sites.
   1.528 @@ -1060,9 +1052,10 @@
   1.529    : (URI | FUNCTION) S*
   1.530    ;</pre>
   1.531  
   1.532 -  <h2 id="&#34;apis&#34;"><span class=secno>8. </span>APIs</h2>
   1.533 +  <h2 id=apis><span class=secno>8. </span>APIs</h2>
   1.534  
   1.535 -  <p>Extensions to the <code>CSSRule</code> interface
   1.536 +  <h3 id=extentions-to-cssrule-interface><span class=secno>8.1. </span>
   1.537 +   Extensions to the <code>CSSRule</code> interface</h3>
   1.538  
   1.539    <p>The <code>CSSRule</code> interface is extended as follows:
   1.540  
   1.541 @@ -1071,16 +1064,15 @@
   1.542      const unsigned short DOCUMENT_RULE = 13;
   1.543  }</pre>
   1.544  
   1.545 -  <h3 id="&#34;the-csssupportsrule-interface&#34;"><span class=secno>8.1.
   1.546 -   </span> The <code>CSSSupportsRule</code> interface</h3>
   1.547 +  <h3 id=the-csssupportsrule-interface><span class=secno>8.2. </span> The
   1.548 +   <code>CSSSupportsRule</code> interface</h3>
   1.549  
   1.550    <p class=issue>Should there be an interface containing the methods common
   1.551     to CSSMediaRule, CSSSupportsRule, and CSSDocumentRule, from which they all
   1.552     derive? Should it be called CSSGroupRule? CSSConditionalRule?
   1.553  
   1.554    <p>The <code>CSSSupportsRule</code> interface represents a ‘<a
   1.555 -   href="#&#34;dfn-support&#34;"><code class=css>@supports</code></a>’
   1.556 -   rule.
   1.557 +   href="#dfn-support"><code class=css>@supports</code></a>’ rule.
   1.558  
   1.559    <pre class=idl>interface CSSSupportsRule : CSSRule {
   1.560      attribute DOMString conditionText;
   1.561 @@ -1115,8 +1107,8 @@
   1.562  
   1.563     <dd>The <code>cssRules</code> attribute must return a
   1.564      <code>CSSRuleList</code> object for the list of CSS rules specified with
   1.565 -    the ‘<a href="#&#34;dfn-support&#34;"><code
   1.566 -    class=css>@supports</code></a>’ rule.
   1.567 +    the ‘<a href="#dfn-support"><code class=css>@supports</code></a>’
   1.568 +    rule.
   1.569    </dl>
   1.570  
   1.571    <dl class=idl-methods>
   1.572 @@ -1136,21 +1128,20 @@
   1.573  
   1.574    <p class=issue>Define the CSSDocumentRule interface.
   1.575  
   1.576 -  <h3 id="&#34;window-api&#34;"><span class=secno>8.2. </span>supportsCSS()
   1.577 -   function</h3>
   1.578 +  <h3 id=window-api><span class=secno>8.3. </span>supportsCSS() function</h3>
   1.579  
   1.580    <pre class=idl>partial interface Window {
   1.581    boolean supportsCSS (DOMString property, DOMString value);
   1.582  };</pre>
   1.583  
   1.584    <p>The <code>supportsCSS</code> function must return <code>true</code> if
   1.585 -   the implementation <a href="#&#34;dfn-support&#34;"><i>supports</i></a>
   1.586 -   the value given by <var>value</var> for the property given by
   1.587 -   <var>property</var>, and <code>false</code> otherwise.
   1.588 +   the implementation <a href="#dfn-support"><i>supports</i></a> the value
   1.589 +   given by <var>value</var> for the property given by <var>property</var>,
   1.590 +   and <code>false</code> otherwise.
   1.591  
   1.592 -  <h2 id="&#34;conformance&#34;"><span class=secno>9. </span>Conformance</h2>
   1.593 +  <h2 id=conformance><span class=secno>9. </span>Conformance</h2>
   1.594  
   1.595 -  <h3 id="&#34;base-modules&#34;"><span class=secno>9.1. </span>Base Modules</h3>
   1.596 +  <h3 id=base-modules><span class=secno>9.1. </span>Base Modules</h3>
   1.597  
   1.598    <p>This specification defines conformance in terms of base modules, which
   1.599     are modules that this specification builds on top of. The base modules of
   1.600 @@ -1183,20 +1174,20 @@
   1.601     such syntax does not make a style sheet nonconformant and failure to treat
   1.602     such syntax as invalid does not make a processor nonconformant.
   1.603  
   1.604 -  <h3 id="&#34;conformance-classes&#34;"><span class=secno>9.2.
   1.605 -   </span>Conformance Classes</h3>
   1.606 +  <h3 id=conformance-classes><span class=secno>9.2. </span>Conformance
   1.607 +   Classes</h3>
   1.608  
   1.609    <p>Conformance to the CSS Conditional Rules Module is defined for three
   1.610     conformance classes:
   1.611  
   1.612    <dl>
   1.613 -   <dt><dfn id="&#34;conform-style-sheet&#34;"
   1.614 -    title="conformance::style sheet">style sheet</dfn>
   1.615 +   <dt><dfn id=conform-style-sheet title="conformance::style sheet">style
   1.616 +    sheet</dfn>
   1.617  
   1.618     <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
   1.619      style sheet</a>.
   1.620  
   1.621 -   <dt><dfn id="&#34;conform-processor&#34;"
   1.622 +   <dt><dfn id=conform-processor
   1.623      title="conformance::processor">processor</dfn>
   1.624  
   1.625     <dd>A tool that reads CSS style sheets: it may be a renderer or <a
   1.626 @@ -1204,7 +1195,7 @@
   1.627      that interprets the semantics of a style sheet and renders documents that
   1.628      use style sheets, or it may be a validator that checks style sheets.
   1.629  
   1.630 -   <dt><dfn id="&#34;conform-authoring-tool&#34;"
   1.631 +   <dt><dfn id=conform-authoring-tool
   1.632      title="conformance::authoring tool">authoring tool</dfn>
   1.633  
   1.634     <dd>A tool that writes a style sheet.
   1.635 @@ -1228,8 +1219,7 @@
   1.636     it writes style sheets that conform to the module and (if it reads CSS) it
   1.637     is a conformant processor.
   1.638  
   1.639 -  <h3 id="&#34;partial&#34;"><span class=secno>9.3. </span> Partial
   1.640 -   Implementations</h3>
   1.641 +  <h3 id=partial><span class=secno>9.3. </span> Partial Implementations</h3>
   1.642  
   1.643    <p>So that authors can exploit the forward-compatible parsing rules to
   1.644     assign fallback values, CSS renderers <strong>must</strong> treat as
   1.645 @@ -1243,7 +1233,7 @@
   1.646     unsupported values must be), CSS requires that the entire declaration be
   1.647     ignored.
   1.648  
   1.649 -  <h3 id="&#34;experimental&#34;"><span class=secno>9.4. </span>Experimental
   1.650 +  <h3 id=experimental><span class=secno>9.4. </span>Experimental
   1.651     Implementations</h3>
   1.652  
   1.653    <p>To avoid clashes with future CSS features, the CSS specifications
   1.654 @@ -1257,8 +1247,7 @@
   1.655     should implement the non-prefixed syntax for any feature they consider to
   1.656     be correctly implemented according to spec.
   1.657  
   1.658 -  <h3 id="&#34;cr-exit-criteria&#34;"><span class=secno>9.5. </span>CR Exit
   1.659 -   Criteria</h3>
   1.660 +  <h3 id=cr-exit-criteria><span class=secno>9.5. </span>CR Exit Criteria</h3>
   1.661  
   1.662    <p>For this specification to be advanced to Proposed Recommendation, there
   1.663     must be at least two independent, interoperable implementations of each
   1.664 @@ -1330,7 +1319,7 @@
   1.665  
   1.666    <h2 class=no-num id=references>References</h2>
   1.667  
   1.668 -  <h3 class=no-num id="&#34;normative-references&#34;">Normative references</h3>
   1.669 +  <h3 class=no-num id=normative-references>Normative references</h3>
   1.670    <!--begin-normative-->
   1.671    <!-- Sorted by label -->
   1.672  
   1.673 @@ -1408,7 +1397,7 @@
   1.674    </dl>
   1.675    <!--end-normative-->
   1.676  
   1.677 -  <h3 class=no-num id="&#34;other-references&#34;">Other references</h3>
   1.678 +  <h3 class=no-num id=other-references>Other references</h3>
   1.679    <!--begin-informative-->
   1.680    <!-- Sorted by label -->
   1.681  
   1.682 @@ -1457,7 +1446,7 @@
   1.683    </dl>
   1.684    <!--end-informative-->
   1.685  
   1.686 -  <h2 class=no-num id="&#34;index&#34;">Index</h2>
   1.687 +  <h2 class=no-num id=index>Index</h2>
   1.688    <!--begin-index-->
   1.689  
   1.690    <ul class=indexlist>
   1.691 @@ -1466,20 +1455,20 @@
   1.692  
   1.693     <li>conformance
   1.694      <ul>
   1.695 -     <li>authoring tool, <a href="#&#34;conform-authoring-tool&#34;"
   1.696 +     <li>authoring tool, <a href="#conform-authoring-tool"
   1.697        title="conformance, authoring tool"><strong>9.2.</strong></a>
   1.698  
   1.699 -     <li>processor, <a href="#&#34;conform-processor&#34;"
   1.700 +     <li>processor, <a href="#conform-processor"
   1.701        title="conformance, processor"><strong>9.2.</strong></a>
   1.702  
   1.703 -     <li>style sheet, <a href="#&#34;conform-style-sheet&#34;"
   1.704 +     <li>style sheet, <a href="#conform-style-sheet"
   1.705        title="conformance, style sheet"><strong>9.2.</strong></a>
   1.706      </ul>
   1.707  
   1.708     <li>‘<code class=css>@document</code>’ rule, <a href="#document-rule"
   1.709      title="'@document' rule"><strong>7.</strong></a>
   1.710  
   1.711 -   <li>domain(), <a href="#&#34;url-domain&#34;"
   1.712 +   <li>domain(), <a href="#url-domain"
   1.713      title="domain()"><strong>7.</strong></a>
   1.714  
   1.715     <li>domain matching function, <a href="#domain-matching-function"
   1.716 @@ -1494,10 +1483,10 @@
   1.717     <li>‘<code class=css>@media</code>’ rule, <a href="#media-rule"
   1.718      title="'@media' rule"><strong>5.</strong></a>
   1.719  
   1.720 -   <li>regexp(), <a href="#&#34;url-regexp&#34;"
   1.721 +   <li>regexp(), <a href="#url-regexp"
   1.722      title="regexp()"><strong>7.</strong></a>
   1.723  
   1.724 -   <li>support, <a href="#&#34;dfn-support&#34;"
   1.725 +   <li>support, <a href="#dfn-support"
   1.726      title=support><strong>6.1.</strong></a>
   1.727  
   1.728     <li>supports_condition, <a href="#supportscondition"
   1.729 @@ -1519,29 +1508,28 @@
   1.730     <li>supports_negation, <a href="#supportsnegation"
   1.731      title="supports_negation"><strong>6.</strong></a>
   1.732  
   1.733 -   <li>‘<a href="#&#34;dfn-support&#34;"><code
   1.734 -    class=css>@supports</code></a>’ rule, <a href="#supports-rule"
   1.735 +   <li>‘<a href="#dfn-support"><code class=css>@supports</code></a>’
   1.736 +    rule, <a href="#supports-rule"
   1.737      title="'@supports' rule"><strong>6.</strong></a>
   1.738  
   1.739     <li>supports_rule, <a href="#supportsrule"
   1.740      title="supports_rule"><strong>6.</strong></a>
   1.741  
   1.742 -   <li>url(), <a href="#&#34;url-exact&#34;"
   1.743 -    title="url()"><strong>7.</strong></a>
   1.744 +   <li>url(), <a href="#url-exact" title="url()"><strong>7.</strong></a>
   1.745  
   1.746     <li>URL matching functions, <a href="#url-matching-functions"
   1.747      title="URL matching functions"><strong>7.</strong></a>
   1.748      <ul>
   1.749 -     <li>domain, <a href="#&#34;url-domain&#34;"
   1.750 +     <li>domain, <a href="#url-domain"
   1.751        title="URL matching functions, domain"><strong>7.</strong></a>
   1.752  
   1.753 -     <li>exact, <a href="#&#34;url-exact&#34;"
   1.754 +     <li>exact, <a href="#url-exact"
   1.755        title="URL matching functions, exact"><strong>7.</strong></a>
   1.756  
   1.757 -     <li>prefix, <a href="#&#34;url-prefix&#34;"
   1.758 +     <li>prefix, <a href="#url-prefix"
   1.759        title="URL matching functions, prefix"><strong>7.</strong></a>
   1.760  
   1.761 -     <li>regular expression, <a href="#&#34;url-regexp&#34;"
   1.762 +     <li>regular expression, <a href="#url-regexp"
   1.763        title="URL matching functions, regular expression"><strong>7.</strong></a>
   1.764      </ul>
   1.765  
   1.766 @@ -1549,7 +1537,7 @@
   1.767      href="#url-of-the-document-being-styled"
   1.768      title="URL of the document being styled"><strong>7.</strong></a>
   1.769  
   1.770 -   <li>url-prefix(), <a href="#&#34;url-prefix&#34;"
   1.771 +   <li>url-prefix(), <a href="#url-prefix"
   1.772      title="url-prefix()"><strong>7.</strong></a>
   1.773  
   1.774     <li>url prefix matching function, <a href="#url-prefix-matching-function"
     2.1 --- a/css3-conditional/Overview.src.html	Fri Aug 31 11:53:59 2012 -0700
     2.2 +++ b/css3-conditional/Overview.src.html	Fri Aug 31 11:57:12 2012 -0700
     2.3 @@ -49,7 +49,7 @@
     2.4  <hr title="Separator for header">
     2.5  </div>
     2.6  
     2.7 -<h2 class="no-num no-toc" id='abstract'>Abstract</h2>
     2.8 +<h2 class="no-num no-toc" id="abstract">Abstract</h2>
     2.9  
    2.10    <p>CSS is a language for describing the rendering of structured documents
    2.11    (such as HTML and XML) on screen, on paper,  in speech, etc. This module
    2.12 @@ -63,7 +63,7 @@
    2.13    the addition of the '@supports' and '@document'
    2.14    rules for conditional processing.
    2.15  
    2.16 -<h2 class="no-num no-toc" id='status'>Status of this document</h2>
    2.17 +<h2 class="no-num no-toc" id="status">Status of this document</h2>
    2.18  
    2.19  <!--status-->
    2.20  
    2.21 @@ -92,13 +92,13 @@
    2.22  
    2.23  </ul>
    2.24  
    2.25 -<h2 class="no-num no-toc" id='"contents"'>Table of contents</h2>
    2.26 +<h2 class="no-num no-toc" id="contents">Table of contents</h2>
    2.27  
    2.28  <!--toc-->
    2.29  
    2.30 -<h2 id='"introduction"'>Introduction</h2>
    2.31 +<h2 id="introduction">Introduction</h2>
    2.32  
    2.33 -<h3 id='"context"'>Background</h3>
    2.34 +<h3 id="context">Background</h3>
    2.35  
    2.36    <p><em>This section is not normative.</em>
    2.37  
    2.38 @@ -134,7 +134,7 @@
    2.39    apply styles to a particular page or group of pages, which greatly
    2.40    increases the power of user style sheets.</p>
    2.41  
    2.42 -<h3 id='"placement"'>Module Interactions</h3>
    2.43 +<h3 id="placement">Module Interactions</h3>
    2.44  
    2.45    <p>This module replaces and extends the '@media' rule
    2.46    feature defined in [[!CSS21]] section <var>7.2.1</var> and
    2.47 @@ -146,7 +146,7 @@
    2.48    assumption that those modules will advance ahead of this one.  If this
    2.49    module advances faster, then the dependency will be reversed.</p>
    2.50  
    2.51 -<h3 id='"conventions"'>Document Conventions</h3>
    2.52 +<h3 id="conventions">Document Conventions</h3>
    2.53  
    2.54    <p>Conformance requirements are expressed with a combination of
    2.55    descriptive assertions and RFC 2119 terminology. The key words “MUST”,
    2.56 @@ -172,7 +172,7 @@
    2.57    
    2.58    <p class="note">Note, this is an informative note.</p>
    2.59  
    2.60 -<h2 id='"processing"'>Processing of conditional group rules</h2>
    2.61 +<h2 id="processing">Processing of conditional group rules</h2>
    2.62  
    2.63  <p>This specification defines some CSS @-rules, called <dfn>conditional
    2.64  group rules</dfn>, that associate a condition with a group of other
    2.65 @@ -232,7 +232,7 @@
    2.66  for some properties in [[CSS3-TRANSITIONS]] and
    2.67  [[!CSS3-ANIMATIONS]]).</p>
    2.68  
    2.69 -<h2 id='"contents-of"'>Contents of conditional group rules</h2>
    2.70 +<h2 id="contents-of">Contents of conditional group rules</h2>
    2.71  
    2.72  <p class="issue">There is also likely demand for using these
    2.73  conditions with '@import'.  We should see if we can
    2.74 @@ -286,7 +286,7 @@
    2.75  href="http://www.w3.org/TR/CSS21/syndata.html#rule-sets">section 4.1.7
    2.76  (Rule sets, declaration blocks, and selectors)</a> of [[!CSS21]].</p>
    2.77  
    2.78 -<h2 id='"use"'>Placement of conditional group rules</h2>
    2.79 +<h2 id="use">Placement of conditional group rules</h2>
    2.80  
    2.81  <p>Conditional group rules are allowed at the top-level of a style
    2.82  sheet, and inside other conditional group rules.  CSS processors
    2.83 @@ -299,7 +299,7 @@
    2.84  not</strong> place such rules after a conditional group rules, and CSS
    2.85  processors <strong>must</strong> ignore such rules.</p>
    2.86  
    2.87 -<h2 id='"at-media"'>Media-specific style sheets:  the '@media' rule</h2>
    2.88 +<h2 id="at-media">Media-specific style sheets:  the '@media' rule</h2>
    2.89  
    2.90  <p>The <dfn>'@media' rule</dfn> is a conditional group rule whose
    2.91  condition is a media query.  It consists of the at-keyword
    2.92 @@ -331,7 +331,7 @@
    2.93  href="http://www.w3.org/TR/CSS21/grammar.html">Grammar of CSS 2.1</a>
    2.94  ([[!CSS21]], Appendix G).
    2.95  
    2.96 -<h2 id='"at-supports"'>Feature queries: the '@supports' rule</h2>
    2.97 +<h2 id="at-supports">Feature queries: the '@supports' rule</h2>
    2.98  
    2.99  <p>The <dfn>'@supports' rule</dfn> is a conditional group
   2.100  rule whose condition tests whether the user agent supports CSS
   2.101 @@ -558,13 +558,13 @@
   2.102  
   2.103  <p class="issue">Add an example involving <code>!important</code>.</p>
   2.104  
   2.105 -<h3 id='"support-definition"'>Definition of support</h3>
   2.106 +<h3 id="support-definition">Definition of support</h3>
   2.107  
   2.108 -<p>A CSS processor is considered to <dfn id='"dfn-support"'>support</dfn>
   2.109 +<p>A CSS processor is considered to <dfn id="dfn-support">support</dfn>
   2.110  a declaration (consisting of a property and value) if it implements the
   2.111  given value of the given property.</p>
   2.112  
   2.113 -<h3 id='"partial-implementations"'>Partial implementations</h3>
   2.114 +<h3 id="partial-implementations">Partial implementations</h3>
   2.115  
   2.116  <p>For forward-compatibility, <a
   2.117  href="http://www.w3.org/TR/CSS21/syndata.html#declaration">section 4.1.8
   2.118 @@ -588,7 +588,7 @@
   2.119  in order to consider the declaration supported, either inside a ruleset
   2.120  or in the declaration condition of an ''@supports'' rule.</p>
   2.121  
   2.122 -<h2 id='"at-document"'>Document queries: the '@document' rule</h2>
   2.123 +<h2 id="at-document">Document queries: the '@document' rule</h2>
   2.124  
   2.125  <p>The <dfn>'@document' rule</dfn> is a conditional group
   2.126  rule whose condition depends on the
   2.127 @@ -603,7 +603,7 @@
   2.128  discouraged?  Or should this specification remain neutral on the
   2.129  topic, since there are valid uses in author style sheets?</p>
   2.130  
   2.131 -<p id='"url-of-doc"'>The <dfn>URL of the document being styled</dfn> is
   2.132 +<p id="url-of-doc">The <dfn>URL of the document being styled</dfn> is
   2.133  the URI at which the document is located, excluding any fragment
   2.134  identifiers.  (This means, for example, that HTTP redirects have been
   2.135  followed.)  If the styles are being applied inside a complete document
   2.136 @@ -638,7 +638,7 @@
   2.137  permitted:</p>
   2.138  
   2.139  <dl>
   2.140 -  <dt><dfn id='"url-exact"' title="url()|URL matching functions::exact">&lt;url&gt;</dfn></dt>
   2.141 +  <dt><dfn id="url-exact" title="url()|URL matching functions::exact">&lt;url&gt;</dfn></dt>
   2.142  
   2.143    <dd>
   2.144      <p>The 'url()' function is the <dfn>exact url matching
   2.145 @@ -663,7 +663,7 @@
   2.146      </div>
   2.147    </dd>
   2.148  
   2.149 -  <dt><dfn id='"url-prefix"' title="url-prefix()|URL matching functions::prefix">url-prefix(&lt;string&gt;)</dfn></dt>
   2.150 +  <dt><dfn id="url-prefix" title="url-prefix()|URL matching functions::prefix">url-prefix(&lt;string&gt;)</dfn></dt>
   2.151  
   2.152    <dd>
   2.153      <p>The 'url-prefix()' function is the <dfn>url prefix
   2.154 @@ -686,7 +686,7 @@
   2.155      </div>
   2.156    </dd>
   2.157  
   2.158 -  <dt><dfn id='"url-domain"' title="domain()|URL matching functions::domain">domain(&lt;string&gt;)</dfn></dt>
   2.159 +  <dt><dfn id="url-domain" title="domain()|URL matching functions::domain">domain(&lt;string&gt;)</dfn></dt>
   2.160  
   2.161    <dd>
   2.162      <p>The 'domain()' function is the <dfn>domain
   2.163 @@ -711,7 +711,7 @@
   2.164      </div>
   2.165    </dd>
   2.166  
   2.167 -  <dt><dfn id='"url-regexp"' title="regexp()|URL matching functions::regular expression">regexp(&lt;string&gt;)</dfn></dt>
   2.168 +  <dt><dfn id="url-regexp" title="regexp()|URL matching functions::regular expression">regexp(&lt;string&gt;)</dfn></dt>
   2.169  
   2.170    <dd>
   2.171      <p>The contents of the &lt;string&gt; argument <strong>must</strong>
   2.172 @@ -760,7 +760,7 @@
   2.173  
   2.174  <div class="issue">This syntax doesn't offer any ability to do negations,
   2.175  which has been requested in <a
   2.176 -href="https://bugzilla.mozilla.org/show_bug.cgi?id='349813"'>Mozilla bug
   2.177 +href="https://bugzilla.mozilla.org/show_bug.cgi?id=349813">Mozilla bug
   2.178  349813</a>.  Use cases that people have wanted negations for
   2.179  include:
   2.180  <ul>
   2.181 @@ -784,9 +784,9 @@
   2.182    : (URI | FUNCTION) S*
   2.183    ;</pre>
   2.184  
   2.185 -<h2 id='"apis"'>APIs</h2>
   2.186 +<h2 id="apis">APIs</h2>
   2.187  
   2.188 -<h3 id=''extentions-to-cssrule-interface''>
   2.189 +<h3 id='extentions-to-cssrule-interface'>
   2.190  Extensions to the <code>CSSRule</code> interface</h3>
   2.191  
   2.192  <p>The <code>CSSRule</code> interface is extended as follows:
   2.193 @@ -797,7 +797,7 @@
   2.194  }</pre>
   2.195  
   2.196  
   2.197 -<h3 id='"the-csssupportsrule-interface"'>
   2.198 +<h3 id="the-csssupportsrule-interface">
   2.199  The <code>CSSSupportsRule</code> interface</h3>
   2.200  
   2.201  <p class="issue">Should there be an interface containing the methods
   2.202 @@ -851,7 +851,7 @@
   2.203  <p class='issue'>Define the CSSDocumentRule interface.
   2.204  
   2.205  
   2.206 -<h3 id='"window-api"'>supportsCSS() function</h3>
   2.207 +<h3 id="window-api">supportsCSS() function</h3>
   2.208  
   2.209  <pre class='idl'>partial interface Window {
   2.210    boolean supportsCSS (DOMString property, DOMString value);
   2.211 @@ -861,9 +861,9 @@
   2.212  if the implementation <i>supports</i> the value given by <var>value</var> for 
   2.213  the property given by <var>property</var>, and <code>false</code> otherwise.
   2.214  
   2.215 -<h2 id='"conformance"'>Conformance</h2>
   2.216 +<h2 id="conformance">Conformance</h2>
   2.217  
   2.218 -<h3 id='"base-modules"'>Base Modules</h3>
   2.219 +<h3 id="base-modules">Base Modules</h3>
   2.220  
   2.221  <p>This specification defines conformance in terms of base modules,
   2.222  which are modules that this specification builds on top of.  The base
   2.223 @@ -893,22 +893,22 @@
   2.224  treat such syntax as invalid does not make a processor
   2.225  nonconformant.</p>
   2.226  
   2.227 -<h3 id='"conformance-classes"'>Conformance Classes</h3>
   2.228 +<h3 id="conformance-classes">Conformance Classes</h3>
   2.229  
   2.230    <p>Conformance to the CSS Conditional Rules Module is defined for three
   2.231    conformance classes:
   2.232    <dl>
   2.233 -    <dt><dfn title="conformance::style sheet" id='"conform-style-sheet"'>style sheet</dfn>
   2.234 +    <dt><dfn title="conformance::style sheet" id="conform-style-sheet">style sheet</dfn>
   2.235        <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
   2.236        style sheet</a>.</dd>
   2.237 -    <dt><dfn title="conformance::processor" id='"conform-processor"'>processor</dfn></dt>
   2.238 +    <dt><dfn title="conformance::processor" id="conform-processor">processor</dfn></dt>
   2.239        <dd>A tool that reads CSS style sheets:  it may be a renderer or
   2.240        <a
   2.241        href="http://www.w3.org/TR/CSS21/conform.html#user-agent">user-agent</a>
   2.242        that interprets the semantics of a style sheet and renders
   2.243        documents that use style sheets, or it may be a validator that
   2.244        checks style sheets.</dd>
   2.245 -    <dt><dfn title="conformance::authoring tool" id='"conform-authoring-tool"'>authoring tool</dfn></dt>
   2.246 +    <dt><dfn title="conformance::authoring tool" id="conform-authoring-tool">authoring tool</dfn></dt>
   2.247        <dd>A tool that writes a style sheet.</dd>
   2.248    </dl>
   2.249  
   2.250 @@ -930,7 +930,7 @@
   2.251    if it writes style sheets that conform to the module and (if it reads
   2.252    CSS) it is a conformant processor.</p>
   2.253  
   2.254 -<h3 id='"partial"'>
   2.255 +<h3 id="partial">
   2.256  Partial Implementations</h3>
   2.257  
   2.258    <p>So that authors can exploit the forward-compatible parsing rules to
   2.259 @@ -944,7 +944,7 @@
   2.260    (as unsupported values must be), CSS requires that the entire declaration
   2.261    be ignored.</p>
   2.262  
   2.263 -<h3 id='"experimental"'>Experimental Implementations</h3>
   2.264 +<h3 id="experimental">Experimental Implementations</h3>
   2.265  
   2.266    <p>To avoid clashes with future CSS features, the CSS specifications
   2.267    reserve a <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
   2.268 @@ -956,7 +956,7 @@
   2.269    should implement the non-prefixed syntax for any feature they consider to
   2.270    be correctly implemented according to spec.</p>
   2.271  
   2.272 -<h3 id='"cr-exit-criteria"'>CR Exit Criteria</h3>
   2.273 +<h3 id="cr-exit-criteria">CR Exit Criteria</h3>
   2.274  
   2.275    <p>For this specification to be advanced to Proposed Recommendation,
   2.276    there must be at least two independent, interoperable implementations
   2.277 @@ -1004,7 +1004,7 @@
   2.278    <p>The specification will remain Candidate Recommendation for at least
   2.279    six months.
   2.280  
   2.281 -<h2 class=no-num id='grammar'>Grammar</h2>
   2.282 +<h2 class=no-num id="grammar">Grammar</h2>
   2.283  
   2.284  <p>In order to allow these new @-rules in CSS style sheets, this
   2.285  specification modifies the <code>stylesheet</code> production in the <a
   2.286 @@ -1014,7 +1014,7 @@
   2.287  and additionally inserting <code>| supports_rule | document_rule</code>
   2.288  alongside <code>ruleset | media | page</code>.</p>
   2.289  
   2.290 -<h2 class=no-num id='acknowledgments'>Acknowledgments</h2>
   2.291 +<h2 class=no-num id="acknowledgments">Acknowledgments</h2>
   2.292  
   2.293  <p>
   2.294  Thanks to the ideas and feedback from
   2.295 @@ -1036,16 +1036,16 @@
   2.296  
   2.297  </p>
   2.298  
   2.299 -<h2 class=no-num id='references'>References</h2>
   2.300 +<h2 class=no-num id="references">References</h2>
   2.301  
   2.302  
   2.303 -<h3 class="no-num" id='"normative-references"'>Normative references</h3>
   2.304 +<h3 class="no-num" id="normative-references">Normative references</h3>
   2.305  <!--normative-->
   2.306  
   2.307 -<h3 class="no-num" id='"other-references"'>Other references</h3>
   2.308 +<h3 class="no-num" id="other-references">Other references</h3>
   2.309  <!--informative-->
   2.310  
   2.311 -<h2 class="no-num" id='"index"'>Index</h2>
   2.312 +<h2 class="no-num" id="index">Index</h2>
   2.313  <!--index-->
   2.314  
   2.315  </body>

mercurial