- From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 04 Aug 2011 16:53:26 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/selectors4 In directory hutz:/tmp/cvs-serv6659 Modified Files: Overview.html Overview.src.html Log Message: Tweak experimental / partial implementation sections to apply properly to selectors Index: Overview.html =================================================================== RCS file: /sources/public/csswg/selectors4/Overview.html,v retrieving revision 1.41 retrieving revision 1.42 diff -u -d -r1.41 -r1.42 --- Overview.html 3 Aug 2011 06:29:29 -0000 1.41 +++ Overview.html 4 Aug 2011 16:53:24 -0000 1.42 @@ -15,13 +15,13 @@ <h1 id=title>Selectors Level 4</h1> - <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 3 August 2011</h2> + <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 4 August 2011</h2> <dl> <dt>This version: - <dd> <!-- <a href="http://www.w3.org/TR/2011/ED-selectors4-20110803/"> - http://www.w3.org/TR/2011/WD-selectors4-20110803</a> --> + <dd> <!-- <a href="http://www.w3.org/TR/2011/ED-selectors4-20110804/"> + http://www.w3.org/TR/2011/WD-selectors4-20110804</a> --> <a href="http://dev.w3.org/csswg/selectors4"> http://dev.w3.org/csswg/selectors4</a> @@ -997,9 +997,11 @@ <li>a selector containing an invalid simple selector, an invalid combinator or an invalid token is invalid. - <li>a group of selectors containing an invalid selector is invalid. + <li>a selector list containing an invalid selector is invalid. </ul> + <p>An invalid selector represents nothing. + <p class=issue>It's been <a href="http://lists.w3.org/Archives/Public/www-style/2010Nov/0203.html">requested</a> that the last rule be dropped in favor of Media Queries-style @@ -3236,18 +3238,16 @@ or excludes, and describing any constraints it adds to the current specification. - <p>Specifications reusing Selectors must define how to handle parsing - errors. (In the case of CSS, the entire rule in which the selector is used - is dropped.) + <p>Specifications reusing Selectors must define how to handle invalid + selectors. (In the case of CSS, the entire rule in which the selector is + used is effectively dropped.) <h3 id=partial><span class=secno>17.2. </span> Partial Implementations</h3> <p>So that authors can exploit the forward-compatible parsing rules to - assign fallback values, CSS renderers <strong>must</strong> treat as - invalid (and <a - href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore as - appropriate</a>) any at-rules, properties, property values, keywords, and - other syntactic constructs for which they have no usable level of support. + assign fallback values, UAs <strong>must</strong> treat as <a + href="#invalid">invalid</a> any selectors for which they have no usable + level of support. <h3 id=experimental><span class=secno>17.3. </span> Experimental Implementations</h3> @@ -3257,11 +3257,11 @@ href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed syntax</a> for proprietary extensions to Selectors. The CSS Working Group recommends that experimental implementations of features in Selectors - Working Drafts also use vendor-prefixed property or value names. This - avoids any incompatibilities with future changes in the draft. Once a - specification reaches the Candidate Recommendation stage, implementors - should implement the non-prefixed syntax for any feature they consider to - be correctly implemented according to spec.</p> + Working Drafts also use vendor-prefixed pseudo-element or pseudo-class + names. This avoids any incompatibilities with future changes in the draft. + Once a specification reaches the Candidate Recommendation stage, + implementors should implement the non-prefixed syntax for any feature they + consider to be correctly implemented according to spec.</p> <!-- <h2 id=Tests>Tests</h2> Index: Overview.src.html =================================================================== RCS file: /sources/public/csswg/selectors4/Overview.src.html,v retrieving revision 1.43 retrieving revision 1.44 diff -u -d -r1.43 -r1.44 --- Overview.src.html 3 Aug 2011 06:29:29 -0000 1.43 +++ Overview.src.html 4 Aug 2011 16:53:24 -0000 1.44 @@ -561,9 +561,11 @@ <li>a simple selector containing an <a href="#namespaces">undeclared namespace prefix</a> is invalid</li> <li>a selector containing an invalid simple selector, an invalid combinator or an invalid token is invalid. </li> - <li>a group of selectors containing an invalid selector is invalid.</li> + <li>a selector list containing an invalid selector is invalid.</li> </ul> + <p>An invalid selector represents nothing. + <p class="issue">It's been <a href="http://lists.w3.org/Archives/Public/www-style/2010Nov/0203.html">requested</a> that the last rule be dropped in favor of Media Queries-style error-handling.</p> @@ -2619,19 +2621,17 @@ subset of Selectors it accepts or excludes, and describing any constraints it adds to the current specification. - <p>Specifications reusing Selectors must define how to handle parsing - errors. (In the case of CSS, the entire rule in which the selector is - used is dropped.)</p> + <p>Specifications reusing Selectors must define how to handle invalid + selectors. (In the case of CSS, the entire rule in which the selector is + used is effectively dropped.)</p> <h3 id="partial"> Partial Implementations</h3> <p>So that authors can exploit the forward-compatible parsing rules to - assign fallback values, CSS renderers <strong>must</strong> - treat as invalid (and <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore - as appropriate</a>) any at-rules, properties, property values, keywords, - and other syntactic constructs for which they have no usable level of - support.</p> + assign fallback values, UAs <strong>must</strong> + treat as <a href="#invalid">invalid</a> any selectors for which they have + no usable level of support.</p> <h3 id="experimental"> Experimental Implementations</h3> @@ -2640,7 +2640,7 @@ reserves a <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed syntax</a> for proprietary extensions to Selectors. The CSS Working Group recommends that experimental implementations of features in Selectors Working - Drafts also use vendor-prefixed property or value names. This + Drafts also use vendor-prefixed pseudo-element or pseudo-class names. This avoids any incompatibilities with future changes in the draft. Once a specification reaches the Candidate Recommendation stage, implementors should implement the non-prefixed syntax for any feature they consider to
Received on Thursday, 4 August 2011 16:53:28 UTC