Regenerate using current preprocessor.

Author: dbaron

css3-conditional/Overview.html

@@ -6,7 +6,7 @@
   content="text/html; charset=utf-8" http-equiv=Content-Type>
 
   <title>CSS Conditional Rules Module Level 3</title>
-  <link href="../css-module/default.css" rel=stylesheet type="text/css">
+  <link href="../default.css" rel=stylesheet type="text/css">
   <link href="http://www.w3.org/StyleSheets/TR/W3C-ED.css" rel=stylesheet
   type="text/css">
 
@@ -17,14 +17,13 @@
 
    <h1>CSS Conditional Rules Module Level 3</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 25 November
-    2011</h2>
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 28 March 2012</h2>
 
    <dl>
     <dt>This version:
 
-    <dd><a href="http://www.w3.org/TR/2011/ED-css3-conditional-20111125/">
-     http://www.w3.org/TR/2011/ED-css3-conditional-20111125/</a>
+    <dd><a href="http://www.w3.org/TR/2012/ED-css3-conditional-20120328/">
+     http://www.w3.org/TR/2012/ED-css3-conditional-20120328/</a>
 
     <dt>Latest version:
 
@@ -67,13 +66,12 @@ <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 25 November
    <!--begin-copyright-->
    <p class=copyright><a
     href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright"
-    rel=license>Copyright</a> &copy; 2011 <a
-    href="http://www.w3.org/"><acronym
-    title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a
-    href="http://www.csail.mit.edu/"><acronym
-    title="Massachusetts Institute of Technology">MIT</acronym></a>, <a
-    href="http://www.ercim.eu/"><acronym
-    title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
+    rel=license>Copyright</a> &copy; 2012 <a href="http://www.w3.org/"><abbr
+    title="World Wide Web Consortium">W3C</abbr></a><sup>&reg;</sup> (<a
+    href="http://www.csail.mit.edu/"><abbr
+    title="Massachusetts Institute of Technology">MIT</abbr></a>, <a
+    href="http://www.ercim.eu/"><abbr
+    title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
     <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a
     href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
     <a
@@ -97,9 +95,9 @@ <h2 class="no-num no-toc" id=abstract>Abstract</h2>
    level&nbsp;1 <a href="#CSS1" rel=biblioentry>[CSS1]<!--{{CSS1}}--></a>.
    The main extensions compared to level&nbsp;2 are allowing nesting of
    certain at-rules inside &lsquo;<code class=css>@media</code>&rsquo;, the
-   addition of the &lsquo;<code class=css>@supports</code>&rsquo; and
-   &lsquo;<code class=css>@document</code>&rsquo; rules for conditional
-   processing.
+   addition of the &lsquo;<a href="#dfn-support"><code
+   class=css>@supports</code></a>&rsquo; and &lsquo;<code
+   class=css>@document</code>&rsquo; rules for conditional processing.
 
   <h2 class="no-num no-toc" id=status>Status of this document</h2>
   <!--begin-status-->
@@ -153,9 +151,10 @@ <h2 class="no-num no-toc" id=status>Status of this document</h2>
     be removed to advance the other features in this specification to
     Proposed Recommendation.
 
-   <li>The &lsquo;<code class=css>@supports</code>&rsquo; rule is at risk; if
-    interoperable implementations are not found, it may be removed to advance
-    the other features in this specification to Proposed Recommendation.
+   <li>The &lsquo;<a href="#dfn-support"><code
+    class=css>@supports</code></a>&rsquo; rule is at risk; if interoperable
+    implementations are not found, it may be removed to advance the other
+    features in this specification to Proposed Recommendation.
 
    <li>The &lsquo;<code class=css>@document</code>&rsquo; rule is at risk; if
     interoperable implementations are not found, it may be removed to advance
@@ -262,15 +261,17 @@ <h3 id=context><span class=secno>1.1. </span>Background</h3>
    single style sheet.
 
   <p>This specification also defines additional types of conditional group
-   rules, &lsquo;<code class=css>@supports</code>&rsquo; and &lsquo;<code
+   rules, &lsquo;<a href="#dfn-support"><code
+   class=css>@supports</code></a>&rsquo; and &lsquo;<code
    class=css>@document</code>&rsquo;, to address author and user
    requirements.
 
-  <p>The &lsquo;<code class=css>@supports</code>&rsquo; rule allows CSS to be
-   conditioned on implementation support for CSS properties and values. This
-   rule makes it much easier for authors to use new CSS features and provide
-   good fallback for implementations that do not support those features. This
-   is particularly important for CSS features that provide new layout
+  <p>The &lsquo;<a href="#dfn-support"><code
+   class=css>@supports</code></a>&rsquo; rule allows CSS to be conditioned on
+   implementation support for CSS properties and values. This rule makes it
+   much easier for authors to use new CSS features and provide good fallback
+   for implementations that do not support those features. This is
+   particularly important for CSS features that provide new layout
    mechanisms, and for other cases where a set of related styles needs to be
    conditioned on property support.
 
@@ -514,7 +515,8 @@ <h2 id=at-media><span class=secno>5. </span>Media-specific style sheets:
    <code>S+</code>. Is that correct?
 
   <h2 id=at-supports><span class=secno>6. </span>Feature queries: the
-   &lsquo;<code class=css>@supports</code>&rsquo; rule</h2>
+   &lsquo;<a href="#dfn-support"><code class=css>@supports</code></a>&rsquo;
+   rule</h2>
 
   <p>The <dfn id=supports-rule>&lsquo;<code class=css>@supports</code>&rsquo;
    rule</dfn> is a conditional group rule whose condition tests whether the
@@ -526,10 +528,10 @@ <h2 id=at-supports><span class=secno>6. </span>Feature queries: the
    tied to the support for certain features, as is the case for use of new
    layout system features.
 
-  <p>The syntax of the condition in the &lsquo;<code
-   class=css>@supports</code>&rsquo; rule is slightly more complicated than
-   for the other conditional group rules (though has some similarities to
-   media queries) since:
+  <p>The syntax of the condition in the &lsquo;<a href="#dfn-support"><code
+   class=css>@supports</code></a>&rsquo; rule is slightly more complicated
+   than for the other conditional group rules (though has some similarities
+   to media queries) since:
 
   <ul>
    <li>negation is needed so that the new-feature styles and the fallback
@@ -544,10 +546,10 @@ <h2 id=at-supports><span class=secno>6. </span>Feature queries: the
     alternatives are vendor-prefixed properties or values
   </ul>
 
-  <p>Therefore, the syntax of the &lsquo;<code
-   class=css>@supports</code>&rsquo; rule allows testing for property:value
-   pairs, and arbitrary conjunctions (and), disjunctions (or), and negations
-   (not) of them.
+  <p>Therefore, the syntax of the &lsquo;<a href="#dfn-support"><code
+   class=css>@supports</code></a>&rsquo; rule allows testing for
+   property:value pairs, and arbitrary conjunctions (and), disjunctions (or),
+   and negations (not) of them.
 
   <p>This extends the lexical scanner in the <a
    href="http://www.w3.org/TR/CSS21/grammar.html">Grammar of CSS 2.1</a> (<a
@@ -593,23 +595,25 @@ <h2 id=at-supports><span class=secno>6. </span>Feature queries: the
    (Tokenization)</a> of <a href="#CSS21"
    rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>.
 
-  <p>Any &lsquo;<code class=css>@supports</code>&rsquo; rule that does not
-   parse according to the grammar above is invalid. Style sheets <strong>must
-   not</strong> use such a rule and processors <strong>must</strong> ignore
-   such a rule.
+  <p>Any &lsquo;<a href="#dfn-support"><code
+   class=css>@supports</code></a>&rsquo; rule that does not parse according
+   to the grammar above is invalid. Style sheets <strong>must not</strong>
+   use such a rule and processors <strong>must</strong> ignore such a rule.
 
   <p class=note>Note that this means that declarations that meet the
    forward-compatible syntax for declarations are permitted (and support for
-   them is then tested by the &lsquo;<code class=css>@supports</code>&rsquo;
-   rule), but declarations that do not meet the forward-compatible syntax for
-   declarations cause the entire &lsquo;<code
-   class=css>@supports</code>&rsquo; rule to be ignored.
+   them is then tested by the &lsquo;<a href="#dfn-support"><code
+   class=css>@supports</code></a>&rsquo; rule), but declarations that do not
+   meet the forward-compatible syntax for declarations cause the entire
+   &lsquo;<a href="#dfn-support"><code class=css>@supports</code></a>&rsquo;
+   rule to be ignored.
 
   <p class=issue>Is any further allowance for forward-compatible parsing
    needed, for example, to allow additional features (such as, say, selector
-   tests) to be added to the &lsquo;<code class=css>@supports</code>&rsquo;
-   rule? Or are these forward-compatible parsing rules the best solution for
-   such future expansion anyway?
+   tests) to be added to the &lsquo;<a href="#dfn-support"><code
+   class=css>@supports</code></a>&rsquo; rule? Or are these
+   forward-compatible parsing rules the best solution for such future
+   expansion anyway?
 
   <p>Each of these grammar terms is associated with a boolean result, as
    follows:
@@ -648,9 +652,10 @@ <h2 id=at-supports><span class=secno>6. </span>Feature queries: the
     href="#support-definition">supports</a> the declaration.
   </dl>
 
-  <p>The condition of the &lsquo;<code class=css>@supports</code>&rsquo; rule
-   is the result of the <code>supports_condition</code> term that is a child
-   of the <code>supports_rule</code> term.
+  <p>The condition of the &lsquo;<a href="#dfn-support"><code
+   class=css>@supports</code></a>&rsquo; rule is the result of the
+   <code>supports_condition</code> term that is a child of the
+   <code>supports_rule</code> term.
 
   <div class=example>
    <p>For example, the following rule</p>
@@ -661,16 +666,16 @@ <h2 id=at-supports><span class=secno>6. </span>Feature queries: the
   #article { background: white; color: black; }
 }</pre>
 
-   <p>applies the rules inside the &lsquo;<code
-    class=css>@supports</code>&rsquo; rule only when &lsquo;<code
+   <p>applies the rules inside the &lsquo;<a href="#dfn-support"><code
+    class=css>@supports</code></a>&rsquo; rule only when &lsquo;<code
     class=css>display: flexbox</code>&rsquo; is supported.</p>
   </div>
 
   <div class=example>
-   <p>The following example shows an additional &lsquo;<code
-    class=css>@supports</code>&rsquo; rule that can be used to provide an
-    alternative for when &lsquo;<code class=css>display:
-    flexbox</code>&rsquo; is not supported:</p>
+   <p>The following example shows an additional &lsquo;<a
+    href="#dfn-support"><code class=css>@supports</code></a>&rsquo; rule that
+    can be used to provide an alternative for when &lsquo;<code
+    class=css>display: flexbox</code>&rsquo; is not supported:</p>
 
    <pre>@supports not ( display: flexbox ) {
   body { width: 100%; height: 100%; background: white; color: black; }
@@ -800,12 +805,13 @@ <h3 id=partial-implementations><span class=secno>6.2. </span>Partial
    use fallback (either in the <a href="#CSS1"
    rel=biblioentry>[CSS1]<!--{{CSS1}}--></a> sense of declarations that are
    overridden by later declarations or with the new capabilities provided by
-   the &lsquo;<code class=css>@supports</code>&rsquo; rule in this
-   specification) that works correctly for the features implemented. This
-   applies especially to compound values; implementations must implement all
-   parts of the value in order to consider the declaration supported, either
-   inside a ruleset or in the declaration condition of an &lsquo;<code
-   class=css>@supports</code>&rsquo; rule.
+   the &lsquo;<a href="#dfn-support"><code
+   class=css>@supports</code></a>&rsquo; rule in this specification) that
+   works correctly for the features implemented. This applies especially to
+   compound values; implementations must implement all parts of the value in
+   order to consider the declaration supported, either inside a ruleset or in
+   the declaration condition of an &lsquo;<a href="#dfn-support"><code
+   class=css>@supports</code></a>&rsquo; rule.
 
   <h2 id=at-document><span class=secno>7. </span>Document queries: the
    &lsquo;<code class=css>@document</code>&rsquo; rule</h2>
@@ -1241,10 +1247,10 @@ <h3 class=no-num id=normative-references>Normative references</h3>
    <dt id=CSS3-FONTS>[CSS3-FONTS]
 
    <dd>John Daggett. <a
-    href="http://www.w3.org/TR/2011/WD-css3-fonts-20110324"><cite>CSS Fonts
-    Module Level 3.</cite></a> 24 March 2011. W3C Working Draft. (Work in
+    href="http://www.w3.org/TR/2011/WD-css3-fonts-20111004/"><cite>CSS Fonts
+    Module Level 3.</cite></a> 4 October 2011. W3C Working Draft. (Work in
     progress.) URL: <a
-    href="http://www.w3.org/TR/2011/WD-css3-fonts-20110324">http://www.w3.org/TR/2011/WD-css3-fonts-20110324</a>
+    href="http://www.w3.org/TR/2011/WD-css3-fonts-20111004/">http://www.w3.org/TR/2011/WD-css3-fonts-20111004/</a>
     </dd>
    <!---->
 
@@ -1381,8 +1387,9 @@ <h2 class=no-num id=index>Index</h2>
    <li>support, <a href="#dfn-support"
     title=support><strong>6.1.</strong></a>
 
-   <li>&lsquo;<code class=css>@supports</code>&rsquo; rule, <a
-    href="#supports-rule" title="'@supports' rule"><strong>6.</strong></a>
+   <li>&lsquo;<a href="#dfn-support"><code
+    class=css>@supports</code></a>&rsquo; rule, <a href="#supports-rule"
+    title="'@supports' rule"><strong>6.</strong></a>
 
    <li>url(), <a href="#url-exact" title="url()"><strong>7.</strong></a>