csswg/css3-conditional Overview.html,1.6,1.7 Overview.src.html,1.6,1.7

Update of /sources/public/csswg/css3-conditional
In directory hutz:/tmp/cvs-serv25298

Modified Files:
	Overview.html Overview.src.html 
Log Message:
Better use of preprocessor features for code.

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-conditional/Overview.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- Overview.html	6 Jun 2011 16:57:31 -0000	1.6
+++ Overview.html	6 Jun 2011 17:07:30 -0000	1.7
@@ -35,15 +35,15 @@
 
     <dd><a
      href="http://www.w3.org/TR/2011/REC-CSS2-2011MMDD/">http://www.w3.org/TR/2011/REC-CSS2-2011MMDD/</a>
-     (<code>@media</code>)
+     (for &lsquo;<code class=css>@media</code>&rsquo;)
 
     <dd><a
      href="http://lists.w3.org/Archives/Public/www-style/2011Apr/0428.html">http://lists.w3.org/Archives/Public/www-style/2011Apr/0428.html</a>
-     (<code>@supports</code>)
+     (for &lsquo;<code class=css>@supports</code>&rsquo;)
 
     <dd><a
      href="http://lists.w3.org/Archives/Public/www-style/2004Aug/0135.html">http://lists.w3.org/Archives/Public/www-style/2004Aug/0135.html</a>
-     (<code>@document</code>)
+     (for &lsquo;<code class=css>@document</code>&rsquo;)
 
     <dt>Editors:
 
@@ -83,8 +83,9 @@
    rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>, which builds on CSS
    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 <code>@media</code>, the addition of the
-   <code>@supports</code> and <code>@document</code> rules for conditional
+   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.
 
   <h2 class="no-num no-toc" id=status>Status of this document</h2>
@@ -125,26 +126,27 @@
   <p>The following features are at risk:
 
   <ul>
-   <li>The inclusion of <code>@font-face</code> rules and
-    <code>@keyframes</code> rules as allowed within all of the @-rules in
-    this specification is at risk, though only because of the relative rates
-    of advancement of specifications. If this specification is able to
-    advance faster than one or both of the specifications defining those
-    rules, then the inclusion of those rules will move from this
-    specification to the specification defining those rules.
+   <li>The inclusion of &lsquo;<code class=css>@font-face</code>&rsquo; rules
+    and &lsquo;<code class=css>@keyframes</code>&rsquo; rules as allowed
+    within all of the @-rules in this specification is at risk, though only
+    because of the relative rates of advancement of specifications. If this
+    specification is able to advance faster than one or both of the
+    specifications defining those rules, then the inclusion of those rules
+    will move from this specification to the specification defining those
+    rules.
 
    <li>The addition of support for @-rules inside of conditional grouping
     rules 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 <code>@supports</code> 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>@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 <code>@document</code> 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
+    the other features in this specification to Proposed Recommendation.
   </ul>
 
   <h2 class="no-num no-toc" id=contents>Table of contents</h2>
@@ -173,13 +175,13 @@
     </ul>
 
    <li><a href="#at-media"><span class=secno>4. </span>Media-specific style
-    sheets: the <code>@media</code> rule</a>
+    sheets: the &lsquo;<code class=css>@media</code>&rsquo; rule</a>
 
    <li><a href="#at-supports"><span class=secno>5. </span>Feature queries:
-    the <code>@supports</code> rule</a>
+    the &lsquo;<code class=css>@supports</code>&rsquo; rule</a>
 
    <li><a href="#at-document"><span class=secno>6. </span>Document queries:
-    the <code>@document</code> rule</a>
+    the &lsquo;<code class=css>@document</code>&rsquo; rule</a>
 
    <li><a href="#conformance"><span class=secno>7. </span>Conformance</a>
     <ul class=toc>
@@ -219,12 +221,14 @@
   <p><em>This section is not normative.</em>
 
   <p><a href="#CSS21" rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a> defines
-   one type of conditional group rule, the <code>@media</code> rule, and
-   allows only rulesets (not other @-rules) inside of it. The
-   <code>@media</code> rule provides the ability to have media-specific style
-   sheets, which is also provided by style sheet linking features such as
-   <code>@import</code> and <code>&lt;link&gt;</code>. The restrictions on
-   the contents of <code>@media</code> rules made them less useful; they have
+   one type of conditional group rule, the &lsquo;<code
+   class=css>@media</code>&rsquo; rule, and allows only rulesets (not other
+   @-rules) inside of it. The &lsquo;<code class=css>@media</code>&rsquo;
+   rule provides the ability to have media-specific style sheets, which is
+   also provided by style sheet linking features such as &lsquo;<code
+   class=css>@import</code>&rsquo; and <code class=html>&lt;link&gt;</code>.
+   The restrictions on the contents of &lsquo;<code
+   class=css>@media</code>&rsquo; rules made them less useful; they have
    forced authors using CSS features involving @-rules in media-specific
    style sheets to use separate style sheets for each medium.
 
@@ -234,29 +238,31 @@
    single style sheet.
 
   <p>This specification also defines additional types of conditional group
-   rules, <code>@supports</code> and <code>@document</code>, to address
-   author and user requirements.
+   rules, &lsquo;<code class=css>@supports</code>&rsquo; and &lsquo;<code
+   class=css>@document</code>&rsquo;, to address author and user
+   requirements.
 
-  <p>The <code>@supports</code> 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;<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
    mechanisms, and for other cases where a set of related styles needs to be
    conditioned on property support.
 
-  <p>The <code>@document</code> rule allows CSS to be conditioned on the page
-   to which the style sheet is being applied. This allows users to apply
-   styles to a particular page or group of pages, which greatly increases the
-   power of user style sheets.
+  <p>The &lsquo;<code class=css>@document</code>&rsquo; rule allows CSS to be
+   conditioned on the page to which the style sheet is being applied. This
+   allows users to apply styles to a particular page or group of pages, which
+   greatly increases the power of user style sheets.
 
   <h3 id=placement><span class=secno>1.2. </span>Module Interactions</h3>
 
-  <p>This module replaces and extends the <code>@media</code> rule feature
-   defined in <a href="#CSS21" rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>
-   section <var>7.2.1</var> and incorporates the modifications previously
-   made non-normatively by <a href="#MEDIAQ"
-   rel=biblioentry>[MEDIAQ]<!--{{!MEDIAQ}}--></a> section <var>1</var>.
+  <p>This module replaces and extends the &lsquo;<code
+   class=css>@media</code>&rsquo; rule feature defined in <a href="#CSS21"
+   rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a> section <var>7.2.1</var> and
+   incorporates the modifications previously made non-normatively by <a
+   href="#MEDIAQ" rel=biblioentry>[MEDIAQ]<!--{{!MEDIAQ}}--></a> section
+   <var>1</var>.
 
   <p>Its current definition depends on @-rules defined in <a href="#CSS3FONT"
    rel=biblioentry>[CSS3FONT]<!--{{!CSS3FONT}}--></a> and <a
@@ -281,15 +287,15 @@
    href="#RFC2119" rel=biblioentry>[RFC2119]<!--{{!RFC2119}}--></a>
 
   <p>Examples in this specification are introduced with the words “for
-   example” or are set apart from the normative text with
-   <code>class="example"</code>, like this:
+   example” or are set apart from the normative text with <code
+   class=html>class="example"</code>, like this:
 
   <div class=example>
    <p>This is an example of an informative example.</p>
   </div>
 
   <p>Informative notes begin with the word “Note” and are set apart from
-   the normative text with <code>class="note"</code>, like this:
+   the normative text with <code class=html>class="note"</code>, like this:
 
   <p class=note>Note, this is an informative note.
 
@@ -346,11 +352,12 @@
    the condition of the rule marked (1) is true for print media, and the
    condition of the rule marked (2) is true when the width of the display
    area (which for print media is the page box) is less than or equal to
-   12cm. Thus the rule <code>#navigation { display: none }</code> applies
-   whenever this style sheet is applied to print media, and the rule
-   <code>.note { float: none }</code> is applied only when the style sheet is
-   applied to print media <em>and</em> the width of the page box is less than
-   or equal to 12 centimeters.</div>
+   12cm. Thus the rule &lsquo;<code class=css>#navigation { display: none
+   }</code>&rsquo; applies whenever this style sheet is applied to print
+   media, and the rule &lsquo;<code class=css>.note { float: none
+   }</code>&rsquo; is applied only when the style sheet is applied to print
+   media <em>and</em> the width of the page box is less than or equal to 12
+   centimeters.</div>
 
   <p>When the condition for a conditional group rule changes, CSS processors
    <strong>must</strong> reflect that the rules now apply or no longer apply,
@@ -365,9 +372,9 @@
    rules</h2>
 
   <p class=issue>There is also likely demand for using these conditions with
-   <code>@import</code>. We should see if we can come up with sensible syntax
-   for that, perhaps functional notation at the end of the
-   <code>@import</code> rule.
+   &lsquo;<code class=css>@import</code>&rsquo;. We should see if we can come
+   up with sensible syntax for that, perhaps functional notation at the end
+   of the &lsquo;<code class=css>@import</code>&rsquo; rule.
 
   <p>The syntax of each conditional group rule consists of some syntax
    specific to the type of rule followed by a <dfn id=group-rule-body>group
@@ -377,9 +384,10 @@
   <p>A group rule body is allowed to contain rulesets and any @-rules that
    are allowed at the top level of a style sheet before and after a ruleset.
    This means that @-rules that must occur at the beginning of the style
-   sheet, such as <code>@charset</code>, <code>@import</code>, and
-   <code>@namespace</code> are not allowed inside of conditional group rules.
-   Conditional group rules can be nested.
+   sheet, such as &lsquo;<code class=css>@charset</code>&rsquo;, &lsquo;<code
+   class=css>@import</code>&rsquo;, and &lsquo;<code
+   class=css>@namespace</code>&rsquo; are not allowed inside of conditional
+   group rules. Conditional group rules can be nested.
 
   <p>In terms of the grammar, this specification defines the following
    productions for use in the grammar of conditional group rules:
@@ -418,26 +426,28 @@
   <p class=issue>Define error handling rules for unknown things.
 
   <h2 id=at-media><span class=secno>4. </span>Media-specific style sheets:
-   the <code>@media</code> rule</h2>
+   the &lsquo;<code class=css>@media</code>&rsquo; rule</h2>
 
-  <p>The <dfn id=media-rule><code>@media</code> rule</dfn> is a conditional
-   group rule whose condition is a media query. It consists of the at-keyword
-   <code>@media</code> followed by a (possibly empty) media query (as defined
-   in <a href="#MEDIAQ" rel=biblioentry>[MEDIAQ]<!--{{!MEDIAQ}}--></a>),
-   followed by a group rule body. The condition of the rule is the result of
-   the media query.
+  <p>The <dfn id=media-rule>&lsquo;<code class=css>@media</code>&rsquo;
+   rule</dfn> is a conditional group rule whose condition is a media query.
+   It consists of the at-keyword &lsquo;<code class=css>@media</code>&rsquo;
+   followed by a (possibly empty) media query (as defined in <a
+   href="#MEDIAQ" rel=biblioentry>[MEDIAQ]<!--{{!MEDIAQ}}--></a>), followed
+   by a group rule body. The condition of the rule is the result of the media
+   query.
 
   <div class=example>
-   <p>This <code>@media</code> rule:</p>
+   <p>This &lsquo;<code class=css>@media</code>&rsquo; rule:</p>
 
    <pre>@media print, (max-width: 600px) {
   #extra_navigation { display: none }
 }</pre>
 
-   <p>has the condition <code>print, (max-width: 600px)</code>, which is true
-    for print media and for devices whose width is at most 600px. When either
-    of these is true, the condition of the rule is true, and the rule
-    <code>#extra_navigation { display: none }</code> is applied.
+   <p>has the condition &lsquo;<code class=css>print, (max-width:
+    600px)</code>&rsquo;, which is true for print media and for devices whose
+    width is at most 600px. When either of these is true, the condition of
+    the rule is true, and the rule &lsquo;<code class=css>#extra_navigation {
+    display: none }</code>&rsquo; is applied.
   </div>
 
   <p>In terms of the grammar, this specification extends the
@@ -461,21 +471,22 @@
    <code>S+</code>. Is that correct?
 
   <h2 id=at-supports><span class=secno>5. </span>Feature queries: the
-   <code>@supports</code> rule</h2>
+   &lsquo;<code class=css>@supports</code>&rsquo; rule</h2>
 
-  <p>The <dfn id=supports-rule><code>@supports</code> rule</dfn> is a
-   conditional group rule whose condition tests whether the user agent
-   supports CSS property:value pairs. Authors can use it to write style
-   sheets that use new features when available but degrade gracefully when
-   those features are not supported. CSS has existing mechanisms for graceful
-   degradation, such as ignoring unsupported properties or values, but these
-   are not always sufficient when large groups of styles need to be tied to
-   the support for certain features, as is the case for use of new layout
-   system features.
+  <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
+   user agent supports CSS property:value pairs. Authors can use it to write
+   style sheets that use new features when available but degrade gracefully
+   when those features are not supported. CSS has existing mechanisms for
+   graceful degradation, such as ignoring unsupported properties or values,
+   but these are not always sufficient when large groups of styles need to be
+   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 <code>@supports</code> 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;<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:
 
   <ul>
    <li>negation is needed so that the new-feature styles and the fallback
@@ -490,9 +501,10 @@
     alternatives are vendor-prefixed properties or values
   </ul>
 
-  <p>Therefore, the syntax of the <code>@supports</code> 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;<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>This extends the lexical scanner in the <a
    href="http://www.w3.org/TR/CSS21/grammar.html">Grammar of CSS 2.1</a> (<a
@@ -568,8 +580,9 @@
     cite.</span>
   </dl>
 
-  <p>and the condition of the <code>@supports</code> rule is the condition
-   thus described for the <code>supports_rule</code> term.
+  <p>and the condition of the &lsquo;<code class=css>@supports</code>&rsquo;
+   rule is the condition thus described for the <code>supports_rule</code>
+   term.
 
   <div class=example>
    <p>For example, the following rule</p>
@@ -580,8 +593,9 @@
   #article { background: white; color: black; }
 }</pre>
 
-   <p>applies the rules inside the <code>@supports</code> rule only when
-    <code>display: flexbox</code> is supported.</p>
+   <p>applies the rules inside the &lsquo;<code
+    class=css>@supports</code>&rsquo; rule only when &lsquo;<code
+    class=css>display: flexbox</code>&rsquo; is supported.</p>
   </div>
 
   <div class=example>
@@ -632,38 +646,39 @@
    layer of parentheses. <span class=issue>Add examples.</span>
 
   <h2 id=at-document><span class=secno>6. </span>Document queries: the
-   <code>@document</code> rule</h2>
+   &lsquo;<code class=css>@document</code>&rsquo; rule</h2>
 
-  <p>The <dfn id=document-rule><code>@document</code> rule</dfn> is a
-   conditional group rule whose condition depends on the URL of the document
-   being styled. This allows style sheets, particularly user style sheets, to
-   have styles that only apply to a set of pages rather than to all pages
-   using the style sheet.
+  <p>The <dfn id=document-rule>&lsquo;<code class=css>@document</code>&rsquo;
+   rule</dfn> is a conditional group rule whose condition depends on the URL
+   of the document being styled. This allows style sheets, particularly user
+   style sheets, to have styles that only apply to a set of pages rather than
+   to all pages using the style sheet.
 
   <p class=issue>Given that this @-rule is intended primarily for user style
    sheets, what should this specification say about its use in author style
    sheets? Should it be forbidden? Should use instead be discouraged? Or
    should this specification remain neutral on the topic?
 
-  <p>The <code>@document</code> rule's condition is written as a
-   comma-separated list of <dfn id=url-matching-functions>URL matching
-   functions</dfn>, and the condition evaluates to true whenever any one of
-   those functions evaluates to true. The following URL matching functions
-   are permitted:
+  <p>The &lsquo;<code class=css>@document</code>&rsquo; rule's condition is
+   written as a comma-separated list of <dfn id=url-matching-functions>URL
+   matching functions</dfn>, and the condition evaluates to true whenever any
+   one of those functions evaluates to true. The following URL matching
+   functions are permitted:
 
   <dl>
    <dt>&lt;url&gt;
 
    <dd>
-    <p>The <code>url()</code> function is the <dfn
+    <p>The &lsquo;<code class=css>url()</code>&rsquo; function is the <dfn
      id=exact-url-matching-function>exact url matching function</dfn>. It
      evaluates to true whenever the URL of the document being styled is
      exactly the URL given.</p>
 
-    <p class=Note>The url() function, since it is a core syntax element in
-     CSS, is allowed (subject to different character limitations and thus
-     escaping requirements) to contain an unquoted value (in addition to the
-     string values that are allowed as arguments for all four functions).</p>
+    <p class=Note>The &lsquo;<code class=css>url()</code>&rsquo; function,
+     since it is a core syntax element in CSS, is allowed (subject to
+     different character limitations and thus escaping requirements) to
+     contain an unquoted value (in addition to the string values that are
+     allowed as arguments for all four functions).</p>
 
     <div class=example>
      <p>For example, this rule:</p>
@@ -672,18 +687,18 @@
   #summary { background: yellow; color: black}
 }</pre>
 
-     <p>styles the <code>summary</code> element on the page
+     <p>styles the <code class=html>summary</code> element on the page
       <code>http://www.w3.org/Style/CSS/</code>, but not on any other pages.</p>
     </div>
 
    <dt>url-prefix(&lt;string&gt;)
 
    <dd>
-    <p>The <code>url-prefix()</code> function is the <dfn
-     id=url-prefix-matching-function>url prefix matching function</dfn>. It
-     evaluates to true whenever the URL of the document being styled has the
-     argument to the function as an initial substring (which is true when the
-     two strings are equal). When the argument is the empty string, it
+    <p>The &lsquo;<code class=css>url-prefix()</code>&rsquo; function is the
+     <dfn id=url-prefix-matching-function>url prefix matching function</dfn>.
+     It evaluates to true whenever the URL of the document being styled has
+     the argument to the function as an initial substring (which is true when
+     the two strings are equal). When the argument is the empty string, it
      evaluates to true for all documents.</p>
 
     <div class=example>
@@ -693,7 +708,7 @@
   #summary { background: yellow; color: black}
 }</pre>
 
-     <p>styles the <code>summary</code> element on the page
+     <p>styles the <code class=html>summary</code> element on the page
       <code>http://www.w3.org/Style/CSS/</code> and on the page
       <code>http://www.w3.org/Style/CSS/Test</code>, but it does not affect
       the page <code>http://www.w3.org/</code> or the page
@@ -703,14 +718,14 @@
    <dt>domain(&lt;string&gt;)
 
    <dd>
-    <p>The <code>domain()</code> function is the <dfn
+    <p>The &lsquo;<code class=css>domain()</code>&rsquo; function is the <dfn
      id=domain-matching-function>domain matching function</dfn>. It evaluates
      to true whenever the URL of the page has a host subcomponent (as defined
      in <a href="#URI" rel=biblioentry>[URI]<!--{{!URI}}--></a>) and that
-     host subcomponent is exactly the argument to the <code>domain()</code>
-     function or a final substring of the host component is a period (U+002E)
-     immediately followed by the argument to the <code>domain()</code>
-     function.</p>
+     host subcomponent is exactly the argument to the &lsquo;<code
+     class=css>domain()</code>&rsquo; function or a final substring of the
+     host component is a period (U+002E) immediately followed by the argument
+     to the &lsquo;<code class=css>domain()</code>&rsquo; function.</p>
 
     <div class=example>
      <p>For example, this rule:</p>
@@ -733,8 +748,9 @@
 
     <p class=note>This definition intentionally matches the behavior of the
      <a
-     href="http://dev.w3.org/html5/spec/common-input-element-attributes.html#attr-input-pattern"><code>pattern</code>
-     attribute</a> on the <code>input</code> element in <a href="#HTML5"
+     href="http://dev.w3.org/html5/spec/common-input-element-attributes.html#attr-input-pattern"><code
+     class=html>pattern</code> attribute</a> on the <code
+     class=html>input</code> element in <a href="#HTML5"
      rel=biblioentry>[HTML5]<!--{{HTML5}}--></a>.</p>
   </dl>
 
@@ -747,9 +763,9 @@
    svg:use.
 
   <p>Implementations <strong>must</strong> treat any unknown URL matching
-   functions as a syntax error, and thus ignore the <code>@document</code>
-   rule. <span class=issue>Should we instead have more complicated error
-   handling rules?</span>
+   functions as a syntax error, and thus ignore the &lsquo;<code
+   class=css>@document</code>&rsquo; rule. <span class=issue>Should we
+   instead have more complicated error handling rules?</span>
 
   <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
@@ -1032,8 +1048,8 @@
    <li>conditional group rules, <a href="#conditional-group-rules"
     title="conditional group rules"><strong>2.</strong></a>
 
-   <li><code>@document</code> rule, <a href="#document-rule" title="@document
-    rule"><strong>6.</strong></a>
+   <li>&lsquo;<code class=css>@document</code>&rsquo; rule, <a
+    href="#document-rule" title="'@document' rule"><strong>6.</strong></a>
 
    <li>domain matching function, <a href="#domain-matching-function"
     title="domain matching function"><strong>6.</strong></a>
@@ -1044,8 +1060,8 @@
    <li>group rule body, <a href="#group-rule-body" title="group rule
     body"><strong>3.</strong></a>
 
-   <li><code>@media</code> rule, <a href="#media-rule" title="@media
-    rule"><strong>4.</strong></a>
+   <li>&lsquo;<code class=css>@media</code>&rsquo; rule, <a
+    href="#media-rule" title="'@media' rule"><strong>4.</strong></a>
 
    <li>renderer, <a href="#renderer" title=renderer><strong>7.1.</strong></a>
     
@@ -1056,8 +1072,8 @@
       conformance class"><strong>7.1.</strong></a>
     </ul>
 
-   <li><code>@supports</code> rule, <a href="#supports-rule" title="@supports
-    rule"><strong>5.</strong></a>
+   <li>&lsquo;<code class=css>@supports</code>&rsquo; rule, <a
+    href="#supports-rule" title="'@supports' rule"><strong>5.</strong></a>
 
    <li>URL matching functions, <a href="#url-matching-functions" title="URL
     matching functions"><strong>6.</strong></a>

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-conditional/Overview.src.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- Overview.src.html	6 Jun 2011 16:57:31 -0000	1.6
+++ Overview.src.html	6 Jun 2011 17:07:30 -0000	1.7
@@ -24,9 +24,9 @@
     <dd><a href="http://www.w3.org/TR/css3-conditional">http://www.w3.org/TR/css3-conditional</a>
 
   <dt>Previous version:
-    <dd><a href="http://www.w3.org/TR/2011/REC-CSS2-2011MMDD/">http://www.w3.org/TR/2011/REC-CSS2-2011MMDD/</a> (<code>@media</code>)</dd>
-    <dd><a href="http://lists.w3.org/Archives/Public/www-style/2011Apr/0428.html">http://lists.w3.org/Archives/Public/www-style/2011Apr/0428.html</a> (<code>@supports</code>)</dd>
-    <dd><a href="http://lists.w3.org/Archives/Public/www-style/2004Aug/0135.html">http://lists.w3.org/Archives/Public/www-style/2004Aug/0135.html</a> (<code>@document</code>)</dd>
+    <dd><a href="http://www.w3.org/TR/2011/REC-CSS2-2011MMDD/">http://www.w3.org/TR/2011/REC-CSS2-2011MMDD/</a> (for '@media')</dd>
+    <dd><a href="http://lists.w3.org/Archives/Public/www-style/2011Apr/0428.html">http://lists.w3.org/Archives/Public/www-style/2011Apr/0428.html</a> (for '@supports')</dd>
+    <dd><a href="http://lists.w3.org/Archives/Public/www-style/2004Aug/0135.html">http://lists.w3.org/Archives/Public/www-style/2004Aug/0135.html</a> (for '@document')</dd>
 
   <dt>Editors:
     <dd class=vcard><a class=fn href="http://dbaron.org/">L. David Baron</a>,
@@ -49,8 +49,8 @@
   It includes and extends the functionality of CSS level&nbsp;2 [[!CSS21]],
   which builds on CSS level&nbsp;1 [[CSS1]].
   The main extensions compared to level&nbsp;2 are
-  allowing nesting of certain at-rules inside <code>@media</code>,
-  the addition of the <code>@supports</code> and <code>@document</code>
+  allowing nesting of certain at-rules inside '@media',
+  the addition of the '@supports' and '@document'
   rules for conditional processing.
 
 <h2 class="no-num no-toc" id=status>Status of this document</h2>
@@ -59,8 +59,8 @@
 
 <p>The following features are at risk:
 <ul>
-  <li>The inclusion of <code>@font-face</code> rules and
-  <code>@keyframes</code> rules as allowed within all of the @-rules in
+  <li>The inclusion of '@font-face' rules and
+  '@keyframes' rules as allowed within all of the @-rules in
   this specification is at risk, though only because of the relative
   rates of advancement of specifications.  If this specification is able
   to advance faster than one or both of the specifications defining
@@ -72,11 +72,11 @@
   may be removed to advance the other features in this specification to
   Proposed Recommendation.</li>
 
-  <li>The <code>@supports</code> rule is at risk; if interoperable
+  <li>The '@supports' 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>
 
-  <li>The <code>@document</code> rule is at risk; if interoperable
+  <li>The '@document' 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>
 
@@ -93,12 +93,12 @@
   <p><em>This section is not normative.</em>
 
   <p>[[!CSS21]] defines one type of conditional group rule, the
-  <code>@media</code> rule, and allows only rulesets (not other @-rules)
-  inside of it.  The <code>@media</code> rule provides the ability to
+  '@media' rule, and allows only rulesets (not other @-rules)
+  inside of it.  The '@media' rule provides the ability to
   have media-specific style sheets, which is also provided by style
-  sheet linking features such as <code>@import</code> and
-  <code>&lt;link&gt;</code>.  The restrictions on the contents of
-  <code>@media</code> rules made them less useful; they have forced authors
+  sheet linking features such as '@import' and
+  <code class="html">&lt;link&gt;</code>.  The restrictions on the contents of
+  '@media' rules made them less useful; they have forced authors
   using CSS features involving @-rules in media-specific style sheets to
   use separate style sheets for each medium.</p>
 
@@ -108,10 +108,10 @@
   sheets within a single style sheet.</p>
 
   <p>This specification also defines additional types of conditional
-  group rules, <code>@supports</code> and <code>@document</code>, to
+  group rules, '@supports' and '@document', to
   address author and user requirements.</p>
 
-  <p>The <code>@supports</code> rule allows CSS to be conditioned on
+  <p>The '@supports' 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
@@ -119,14 +119,14 @@
   mechanisms, and for other cases where a set of related styles needs to
   be conditioned on property support.</p>
 
-  <p>The <code>@document</code> rule allows CSS to be conditioned on the
+  <p>The '@document' rule allows CSS to be conditioned on the
   page to which the style sheet is being applied.  This allows users to
   apply styles to a particular page or group of pages, which greatly
   increases the power of user style sheets.</p>
 
 <h3 id="placement">Module Interactions</h3>
 
-  <p>This module replaces and extends the <code>@media</code> rule
+  <p>This module replaces and extends the '@media' rule
   feature defined in [[!CSS21]] section <var>7.2.1</var> and
   incorporates the modifications previously made non-normatively by
   [[!MEDIAQ]] section <var>1</var>.</p>
@@ -150,15 +150,15 @@
   explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p>
   
   <p>Examples in this specification are introduced with the words “for example”
-  or are set apart from the normative text with <code>class="example"</code>,
-  like this:
+  or are set apart from the normative text with
+  <code class="html">class="example"</code>, like this:
   
   <div class="example">
     <p>This is an example of an informative example.</p>
   </div>
   
   <p>Informative notes begin with the word “Note” and are set apart from the
-  normative text with <code>class="note"</code>, like this:
+  normative text with <code class="html">class="note"</code>, like this:
   
   <p class="note">Note, this is an informative note.</p>
 
@@ -209,9 +209,9 @@
 the condition of the rule marked (1) is true for print media, and the
 condition of the rule marked (2) is true when the width of the display
 area (which for print media is the page box) is less than or equal to
-12cm.  Thus the rule <code>#navigation { display: none }</code> applies
+12cm.  Thus the rule ''#navigation { display: none }'' applies
 whenever this style sheet is applied to print media, and the rule
-<code>.note { float: none }</code> is applied only when the style sheet
+''.note { float: none }'' is applied only when the style sheet
 is applied to print media <em>and</em> the width of the page box is less
 than or equal to 12 centimeters.</div>
 
@@ -225,9 +225,9 @@
 <h2 id="contents">Contents of conditional group rules</h2>
 
 <p class="issue">There is also likely demand for using these
-conditions with <code>@import</code>.  We should see if we can
+conditions with '@import'.  We should see if we can
 come up with sensible syntax for that, perhaps functional notation
-at the end of the <code>@import</code> rule.</p>
+at the end of the '@import' rule.</p>
 
 <p>The syntax of each conditional group rule consists of some syntax
 specific to the type of rule followed by a <dfn>group rule body</dfn>,
@@ -236,8 +236,8 @@
 <p>A group rule body is allowed to contain rulesets and any @-rules that
 are allowed at the top level of a style sheet before and after a
 ruleset.  This means that @-rules that must occur at the beginning of
-the style sheet, such as <code>@charset</code>, <code>@import</code>,
-and <code>@namespace</code> are not allowed inside of conditional group
+the style sheet, such as '@charset', '@import',
+and '@namespace' are not allowed inside of conditional group
 rules.  Conditional group rules can be nested.</p>
 
 <p>In terms of the grammar, this specification defines the following
@@ -273,23 +273,23 @@
 
 <p class="issue">Define error handling rules for unknown things.</p>
 
-<h2 id="at-media">Media-specific style sheets:  the <code>@media</code> rule</h2>
+<h2 id="at-media">Media-specific style sheets:  the '@media' rule</h2>
 
-<p>The <dfn><code>@media</code> rule</dfn> is a conditional group rule whose
+<p>The <dfn>'@media' rule</dfn> is a conditional group rule whose
 condition is a media query.  It consists of the at-keyword
-<code>@media</code> followed by a (possibly empty) media query (as
+'@media' followed by a (possibly empty) media query (as
 defined in [[!MEDIAQ]]), followed by a group rule body.  The condition
 of the rule is the result of the media query.</p>
 
 <div class="example">
-<p>This <code>@media</code> rule:</p>
+<p>This '@media' rule:</p>
 <pre>@media print, (max-width: 600px) {
   #extra_navigation { display: none }
 }</pre>
-<p>has the condition <code>print, (max-width: 600px)</code>, which is
+<p>has the condition ''print, (max-width: 600px)'', which is
 true for print media and for devices whose width is at most 600px.  When
 either of these is true, the condition of the rule is true, and the rule
-<code>#extra_navigation { display: none }</code> is applied.
+''#extra_navigation { display: none }'' is applied.
 </div>
 
 <p>In terms of the grammar, this specification extends the
@@ -308,9 +308,9 @@
 <p class="issue">This changes the <code>S*</code> in CSS 2.1 into
 <code>S+</code>.  Is that correct?</p>
 
-<h2 id="at-supports">Feature queries: the <code>@supports</code> rule</h2>
+<h2 id="at-supports">Feature queries: the '@supports' rule</h2>
 
-<p>The <dfn><code>@supports</code> rule</dfn> is a conditional group
+<p>The <dfn>'@supports' rule</dfn> is a conditional group
 rule whose condition tests whether the user agent supports CSS
 property:value pairs.  Authors can use it to write style sheets that use
 new features when available but degrade gracefully when those features
@@ -320,7 +320,7 @@
 tied to the support for certain features, as is the case for use of new
 layout system features.</p>
 
-<p>The syntax of the condition in the <code>@supports</code> rule is
+<p>The syntax of the condition in the '@supports' rule is
 slightly more complicated than for the other conditional group rules
 (though has some similarities to media queries) since:</p>
 <ul>
@@ -334,7 +334,7 @@
   alternatives are vendor-prefixed properties or values</li>
 </ul>
 
-<p>Therefore, the syntax of the <code>@supports</code> rule allows
+<p>Therefore, the syntax of the '@supports' rule allows
 testing for property:value pairs, and arbitrary conjunctions (and),
 disjunctions (or), and negations (not) of them.</p>
 
@@ -410,7 +410,7 @@
 </dd>
 </dl>
 
-<p>and the condition of the <code>@supports</code> rule is the
+<p>and the condition of the '@supports' rule is the
 condition thus described for the <code>supports_rule</code> term.</p>
 
 <div class="example">
@@ -420,8 +420,8 @@
   #navigation { background: blue; color: white; }
   #article { background: white; color: black; }
 }</pre>
-<p>applies the rules inside the <code>@supports</code> rule only when
-<code>display: flexbox</code> is supported.</p>
+<p>applies the rules inside the '@supports' rule only when
+''display: flexbox'' is supported.</p>
 </div>
 
 <div class="example">
@@ -465,9 +465,9 @@
 examples.</span></p>
 
 
-<h2 id="at-document">Document queries: the <code>@document</code> rule</h2>
+<h2 id="at-document">Document queries: the '@document' rule</h2>
 
-<p>The <dfn><code>@document</code> rule</dfn> is a conditional group
+<p>The <dfn>'@document' rule</dfn> is a conditional group
 rule whose condition depends on the URL of the document being styled.
 This allows style sheets, particularly user style sheets, to have styles
 that only apply to a set of pages rather than to all pages using the
@@ -479,7 +479,7 @@
 discouraged?  Or should this specification remain neutral on the
 topic?</p>
 
-<p>The <code>@document</code> rule's condition is written as a
+<p>The '@document' rule's condition is written as a
 comma-separated list of <dfn>URL matching functions</dfn>, and the
 condition evaluates to true whenever any one of those functions
 evaluates to true.  The following URL matching functions are
@@ -489,11 +489,11 @@
   <dt>&lt;url&gt;</dt>
 
   <dd>
-    <p>The <code>url()</code> function is the <dfn>exact url matching
+    <p>The 'url()' function is the <dfn>exact url matching
     function</dfn>.  It evaluates to true whenever the URL of the
     document being styled is exactly the URL given.</p>
 
-    <p class="Note">The url() function, since it is a core syntax
+    <p class="Note">The 'url()' function, since it is a core syntax
     element in CSS, is allowed (subject to different character
     limitations and thus escaping requirements) to contain an unquoted
     value (in addition to the string values that are allowed as
@@ -504,7 +504,7 @@
 <pre>@document url("http://www.w3.org/Style/CSS/") {
   #summary { background: yellow; color: black}
 }</pre>
-      <p>styles the <code>summary</code> element on the page
+      <p>styles the <code class="html">summary</code> element on the page
       <code>http://www.w3.org/Style/CSS/</code>, but not on any other
       pages.</p>
     </div>
@@ -513,7 +513,7 @@
   <dt>url-prefix(&lt;string&gt;)</dt>
 
   <dd>
-    <p>The <code>url-prefix()</code> function is the <dfn>url prefix
+    <p>The 'url-prefix()' function is the <dfn>url prefix
     matching function</dfn>.  It evaluates to true whenever the URL of
     the document being styled has the argument to the function as an
     initial substring (which is true when the two strings are equal).
@@ -524,7 +524,7 @@
 <pre>@document url-prefix("http://www.w3.org/Style/CSS/") {
   #summary { background: yellow; color: black}
 }</pre>
-      <p>styles the <code>summary</code> element on the page
+      <p>styles the <code class="html">summary</code> element on the page
       <code>http://www.w3.org/Style/CSS/</code> and on the page
       <code>http://www.w3.org/Style/CSS/Test</code>, but it does not
       affect the page <code>http://www.w3.org/</code> or the page
@@ -535,13 +535,13 @@
   <dt>domain(&lt;string&gt;)</dt>
 
   <dd>
-    <p>The <code>domain()</code> function is the <dfn>domain
+    <p>The 'domain()' function is the <dfn>domain
     matching function</dfn>.  It evaluates to true whenever
     the URL of the page has a host subcomponent (as defined in [[!URI]])
     and that host subcomponent is exactly the argument to the
-    <code>domain()</code> function or a final substring of the host
+    'domain()' function or a final substring of the host
     component is a period (U+002E) immediately followed by the argument
-    to the <code>domain()</code> function.</p>
+    to the 'domain()' function.</p>
     <div class="example">
       <p>For example, this rule:</p>
 <pre>@document domain("w3.org") {
@@ -563,8 +563,9 @@
 
     <p class="note">This definition intentionally matches the behavior
     of the <a
-    href="http://dev.w3.org/html5/spec/common-input-element-attributes.html#attr-input-pattern"><code>pattern</code>
-    attribute</a> on the <code>input</code> element in [[HTML5]].</p>
+    href="http://dev.w3.org/html5/spec/common-input-element-attributes.html#attr-input-pattern"><code class="html">pattern</code>
+    attribute</a> on the <code class="html">input</code> element
+    in [[HTML5]].</p>
   </dd>
 
 </dl>
@@ -578,7 +579,7 @@
 svg:use.</p>
 
 <p>Implementations <strong>must</strong> treat any unknown URL matching
-functions as a syntax error, and thus ignore the <code>@document</code>
+functions as a syntax error, and thus ignore the '@document'
 rule.  <span class="issue">Should we instead have more complicated error
 handling rules?</span></p>
 

Received on Monday, 6 June 2011 17:07:35 UTC