Mercurial > drafts / changeset

     1.1 --- a/css3-conditional/Overview.html	Thu Oct 11 22:57:09 2012 -0700
     1.2 +++ b/css3-conditional/Overview.html	Thu Oct 11 23:43:33 2012 -0700
     1.3 @@ -162,9 +162,6 @@
     1.4     <li>The ‘<code class=css>@supports</code>’ rule is at risk; if
     1.5      interoperable implementations are not found, it may be removed to advance
     1.6      the other features in this specification to Proposed Recommendation.
     1.7 -
     1.8 -   <li>The support for functions inside of ‘<code
     1.9 -    class=css>@supports</code>’ is at risk.
    1.10    </ul>
    1.11    <!--
    1.12  
    1.13 @@ -652,8 +649,11 @@
    1.14  
    1.15     <dt>supports_declaration_condition
    1.16  
    1.17 -   <dd> The result is whether the CSS processor <a
    1.18 -    href="#support-definition">supports</a> the declaration or function.
    1.19 +   <dd> The result is false if this corresponds to a functional notation;
    1.20 +    otherwise, the result is whether the CSS processor <a
    1.21 +    href="#support-definition">supports</a> the declaration within the
    1.22 +    parentheses. <span class=note>Note that future levels may define
    1.23 +    functions that can evaluate to true.</span>
    1.24    </dl>
    1.25  
    1.26    <p>The condition of the ‘<code class=css>@supports</code>’ rule is the
    1.27 @@ -813,13 +813,6 @@
    1.28     it <strong>must not</strong> accept the declaration or claim support for
    1.29     it.
    1.30  
    1.31 -  <p>A CSS processor is considered to <a
    1.32 -   href="#dfn-support"><i>support</i></a> a function (consisting of a
    1.33 -   function name and arguments) if it accepts that function (rather than
    1.34 -   discarding it as a parse error). If a processor does not implement, with a
    1.35 -   usable level of support, the value given, then it <strong>must
    1.36 -   not</strong> accept the function or claim support for it.
    1.37 -
    1.38    <p>These rules (and the equivalence between them) allow authors to use
    1.39     fallback (either in the <a href="#CSS1"
    1.40     rel=biblioentry>[CSS1]<!--{{CSS1}}--></a> sense of declarations that are
    1.41 @@ -1370,6 +1363,10 @@
    1.42     September 2012 Working Draft</a>:
    1.43  
    1.44    <ul>
    1.45 +   <li>Allow functional notation in ‘<code class=css>@supports</code>’
    1.46 +    queries to be valid (to allow for future extensions), but treat such
    1.47 +    notations as always being false.
    1.48 +
    1.49     <li>Corrected the grammar as follows:
    1.50      <pre>
    1.51  -  : SUPPORTS_SYM S+ supports_condition group_rule_body

     2.1 --- a/css3-conditional/Overview.src.html	Thu Oct 11 22:57:09 2012 -0700
     2.2 +++ b/css3-conditional/Overview.src.html	Thu Oct 11 23:43:33 2012 -0700
     2.3 @@ -89,8 +89,6 @@
     2.4    <li>The '@supports' rule is at risk; if interoperable
     2.5    implementations are not found, it may be removed to advance the other
     2.6    features in this specification to Proposed Recommendation.</li>
     2.7 -
     2.8 -  <li>The support for functions inside of ''@supports'' is at risk.</li>
     2.9  </ul>
    2.10  
    2.11  <!--
    2.12 @@ -444,8 +442,11 @@
    2.13  
    2.14  <dt>supports_declaration_condition</dt>
    2.15  <dd>
    2.16 -  The result is whether the CSS processor <a
    2.17 -  href="#support-definition">supports</a> the declaration or function.
    2.18 +  The result is false if this corresponds to a functional notation;
    2.19 +  otherwise, the result is whether the CSS processor <a
    2.20 +  href="#support-definition">supports</a> the declaration
    2.21 +  within the parentheses.
    2.22 +  <span class="note">Note that future levels may define functions that can evaluate to true.</span>
    2.23  </dd>
    2.24  </dl>
    2.25  
    2.26 @@ -582,15 +583,6 @@
    2.27  then it <strong>must not</strong>
    2.28  accept the declaration or claim support for it.</p>
    2.29  
    2.30 -<p>A CSS processor is considered to <i>support</i> a function 
    2.31 -(consisting of a function name and arguments)
    2.32 -if it accepts that function
    2.33 -(rather than discarding it as a parse error).
    2.34 -If a processor does not implement, with a usable level of support,
    2.35 -the value given,
    2.36 -then it <strong>must not</strong>
    2.37 -accept the function or claim support for it.</p>
    2.38 -
    2.39  <p>These rules (and the equivalence between them) allow
    2.40  authors to use fallback (either in the [[CSS1]] sense of declarations
    2.41  that are overridden by later declarations or with the new capabilities
    2.42 @@ -1116,6 +1108,8 @@
    2.43  <a href="http://www.w3.org/TR/2012/WD-css3-conditional-20120911/">11 September 2012 Working Draft</a>:
    2.44  
    2.45  <ul>
    2.46 +  <li>Allow functional notation in ''@supports'' queries to be valid (to allow for future extensions),
    2.47 +      but treat such notations as always being false.
    2.48    <li>Corrected the grammar as follows:
    2.49  <pre>
    2.50  -  : SUPPORTS_SYM S+ supports_condition group_rule_body