Merge sections on definition-of-support and partial-implementations and rewrite to address feedback in http://lists.w3.org/Archives/Public/www-style/2012Sep/0370.html .

Thu, 20 Sep 2012 13:03:53 -0700

author
L. David Baron <dbaron@dbaron.org>
date
Thu, 20 Sep 2012 13:03:53 -0700
changeset 6741
ce28a0e42de9
parent 6740
37b94dbfec45
child 6742
911a391cb16c

Merge sections on definition-of-support and partial-implementations and rewrite to address feedback in http://lists.w3.org/Archives/Public/www-style/2012Sep/0370.html .

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	Thu Sep 20 12:43:23 2012 -0700
     1.2 +++ b/css3-conditional/Overview.html	Thu Sep 20 13:03:53 2012 -0700
     1.3 @@ -201,9 +201,6 @@
     1.4      <ul class=toc>
     1.5       <li><a href="#support-definition"><span class=secno>6.1.
     1.6        </span>Definition of support</a>
     1.7 -
     1.8 -     <li><a href="#partial-implementations"><span class=secno>6.2.
     1.9 -      </span>Partial implementations</a>
    1.10      </ul>
    1.11  
    1.12     <li><a href="#at-document"><span class=secno>7. </span>Document queries:
    1.13 @@ -809,38 +806,35 @@
    1.14    <h3 id=support-definition><span class=secno>6.1. </span>Definition of
    1.15     support</h3>
    1.16  
    1.17 -  <p>A CSS processor is considered to <dfn id=dfn-support>support</dfn> a
    1.18 -   declaration (consisting of a property and value) if it implements the
    1.19 -   given value of the given property.
    1.20 -
    1.21 -  <h3 id=partial-implementations><span class=secno>6.2. </span>Partial
    1.22 -   implementations</h3>
    1.23 -
    1.24    <p>For forward-compatibility, <a
    1.25     href="http://www.w3.org/TR/CSS21/syndata.html#declaration">section 4.1.8
    1.26     (Declarations and properties)</a> of <a href="#CSS21"
    1.27     rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a> defines rules for handling
    1.28 -   invalid properties and values. CSS processors that partially implement a
    1.29 -   specification <strong>must</strong> treat any part of a value that they:
    1.30 +   invalid properties and values. CSS processors that do not implement or
    1.31 +   partially implement a specification <strong>must</strong> treat any part
    1.32 +   of a value that they do not implement, or do not have a usable level of
    1.33 +   support for, as invalid according to this rule for handling invalid
    1.34 +   properties and values, and therefore <strong>must</strong> discard the
    1.35 +   declaration as a parse error.
    1.36  
    1.37 -  <ul>
    1.38 -   <li>do not implement, or
    1.39 +  <p>A CSS processor is considered to <dfn id=dfn-support>support</dfn> a
    1.40 +   declaration (consisting of a property and value) if it accepts that
    1.41 +   declaration (rather than discarding it as a parse error). If a processor
    1.42 +   does not implement, with a usable level of support, the value given, then
    1.43 +   it <strong>must not</strong> accept the declaration or claim support for
    1.44 +   it.
    1.45  
    1.46 -   <li>do not have a usable level of support for,
    1.47 -  </ul>
    1.48 -
    1.49 -  <p>as invalid according to this rule for handling invalid properties and
    1.50 -   values, and <strong>must not</strong> accept or support a declaration
    1.51 -   containing such a value. This allows authors to use fallback (either in
    1.52 -   the <a href="#CSS1" rel=biblioentry>[CSS1]<!--{{CSS1}}--></a> sense of
    1.53 -   declarations that are overridden by later declarations or with the new
    1.54 -   capabilities provided by the ‘<a href="#dfn-support"><code
    1.55 -   class=css>@supports</code></a>’ rule in this specification) that works
    1.56 -   correctly for the features implemented. This applies especially to
    1.57 -   compound values; implementations must implement all parts of the value in
    1.58 -   order to consider the declaration supported, either inside a ruleset or in
    1.59 -   the declaration condition of an ‘<a href="#dfn-support"><code
    1.60 -   class=css>@supports</code></a>’ rule.
    1.61 +  <p>This equivalence between declaration acceptance and ‘<a
    1.62 +   href="#dfn-support"><code class=css>@supports</code></a>’ allows authors
    1.63 +   to use fallback (either in the <a href="#CSS1"
    1.64 +   rel=biblioentry>[CSS1]<!--{{CSS1}}--></a> sense of declarations that are
    1.65 +   overridden by later declarations or with the new capabilities provided by
    1.66 +   the ‘<a href="#dfn-support"><code class=css>@supports</code></a>’ rule
    1.67 +   in this specification) that works correctly for the features implemented.
    1.68 +   This applies especially to compound values; implementations must implement
    1.69 +   all parts of the value in order to consider the declaration supported,
    1.70 +   either inside a ruleset or in the declaration condition of an ‘<a
    1.71 +   href="#dfn-support"><code class=css>@supports</code></a>’ rule.
    1.72  
    1.73    <h2 id=at-document><span class=secno>7. </span>Document queries: the
    1.74     ‘<code class=css>@document</code>’ rule</h2>
     2.1 --- a/css3-conditional/Overview.src.html	Thu Sep 20 12:43:23 2012 -0700
     2.2 +++ b/css3-conditional/Overview.src.html	Thu Sep 20 13:03:53 2012 -0700
     2.3 @@ -564,26 +564,28 @@
     2.4  
     2.5  <h3 id="support-definition">Definition of support</h3>
     2.6  
     2.7 +<p>For forward-compatibility,
     2.8 +<a href="http://www.w3.org/TR/CSS21/syndata.html#declaration">section 4.1.8
     2.9 +(Declarations and properties)</a> of [[!CSS21]]
    2.10 +defines rules for handling invalid properties and values.
    2.11 +CSS processors that
    2.12 +do not implement or partially implement a specification
    2.13 +<strong>must</strong> treat any part of a value that they
    2.14 +do not implement, or
    2.15 +do not have a usable level of support for,
    2.16 +as invalid according to this rule
    2.17 +for handling invalid properties and values,
    2.18 +and therefore <strong>must</strong> discard the declaration as a parse error.</p>
    2.19 +
    2.20  <p>A CSS processor is considered to <dfn id="dfn-support">support</dfn>
    2.21 -a declaration (consisting of a property and value) if it implements the
    2.22 -given value of the given property.</p>
    2.23 +a declaration (consisting of a property and value) if it accepts that
    2.24 +declaration (rather than discarding it as a parse error).
    2.25 +If a processor does not implement, with a usable level of support,
    2.26 +the value given,
    2.27 +then it <strong>must not</strong>
    2.28 +accept the declaration or claim support for it.</p>
    2.29  
    2.30 -<h3 id="partial-implementations">Partial implementations</h3>
    2.31 -
    2.32 -<p>For forward-compatibility, <a
    2.33 -href="http://www.w3.org/TR/CSS21/syndata.html#declaration">section 4.1.8
    2.34 -(Declarations and properties)</a> of [[!CSS21]] defines rules for
    2.35 -handling invalid properties and values.  CSS processors that partially
    2.36 -implement a specification <strong>must</strong> treat any part of a
    2.37 -value that they:</p>
    2.38 -<ul>
    2.39 -  <li>do not implement, or</li>
    2.40 -  <li>do not have a usable level of support for,</li>
    2.41 -</ul>
    2.42 -<p>as invalid according to this rule
    2.43 -for handling invalid properties and values,
    2.44 -and <strong>must not</strong>
    2.45 -accept or support a declaration containing such a value.  This allows
    2.46 +<p>This equivalence between declaration acceptance and ''@supports'' allows
    2.47  authors to use fallback (either in the [[CSS1]] sense of declarations
    2.48  that are overridden by later declarations or with the new capabilities
    2.49  provided by the ''@supports'' rule in this specification) that works

mercurial