Mon, 15 Oct 2012 11:37:14 -0700
[selectors4] scope-constrained renamed to scope-filtered
selectors4/Overview.html | file | annotate | diff | comparison | revisions | |
selectors4/Overview.src.html | file | annotate | diff | comparison | revisions |
1.1 --- a/selectors4/Overview.html Fri Oct 12 15:30:09 2012 -0700 1.2 +++ b/selectors4/Overview.html Mon Oct 15 11:37:14 2012 -0700 1.3 @@ -4,16 +4,16 @@ 1.4 <head profile="http://dublincore.org/documents/2008/08/04/dc-html/ "> 1.5 <title>Selectors Level 4</title> 1.6 1.7 - <link href="http://purl.org/dc/terms/" rel=schema.DC> 1.8 - <meta content="Selectors Level 4" name=DC.title> 1.9 - <meta content=text name=DC.type> 1.10 - <meta content=2012-09-05 name=DC.issued> 1.11 - <meta content="http://dev.w3.org/csswg/selectors4/" name=DC.creator> 1.12 - <meta content=W3C name=DC.publisher> 1.13 - <meta content="http://www.w3.org/TR/2012/ED-selectors4-20120905/" 1.14 - name=DC.identifier> 1.15 + <link href="http://purl.org/dc/terms/" rel=schema.dcterms> 1.16 <link href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright" 1.17 - rel=DC.rights> 1.18 + rel=dcterms.rights> 1.19 + <meta content="Selectors Level 4" name=dcterms.title> 1.20 + <meta content=text name=dcterms.type> 1.21 + <meta content=2012-10-15 name=dcterms.issued> 1.22 + <meta content="http://dev.w3.org/csswg/selectors4/" name=dcterms.creator> 1.23 + <meta content=W3C name=dcterms.publisher> 1.24 + <meta content="http://www.w3.org/TR/2012/ED-selectors4-20121015/" 1.25 + name=dcterms.identifier> 1.26 <link href="../default.css" rel=stylesheet type="text/css"> 1.27 <style type="text/css"> 1.28 .tprofile td, th { vertical-align: baseline; padding: 0 0.5em; } 1.29 @@ -29,14 +29,14 @@ 1.30 1.31 <h1 id=title>Selectors Level 4</h1> 1.32 1.33 - <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 5 September 1.34 + <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 15 October 1.35 2012</h2> 1.36 1.37 <dl> 1.38 <dt>This version: 1.39 1.40 - <dd><a href="http://www.w3.org/TR/2012/ED-selectors4-20120905/"> 1.41 - http://www.w3.org/TR/2012/ED-selectors4-20120905/</a> 1.42 + <dd><a href="http://www.w3.org/TR/2012/ED-selectors4-20121015/"> 1.43 + http://www.w3.org/TR/2012/ED-selectors4-20121015/</a> 1.44 1.45 <dt>Editor's draft: 1.46 1.47 @@ -1247,7 +1247,7 @@ 1.48 href="#roo-pseudo"><code>:root</code></a> pseudo-class, however, still 1.49 only matches the actual root of the document.) 1.50 1.51 - <dt><dfn id=scope-constrained>scope-constrained</dfn> selectors 1.52 + <dt><dfn id=scope-filtered>scope-filtered</dfn> selectors 1.53 1.54 <dd> With this method of scoping, a selector matches if the <i>subject</i> 1.55 of the selector is within the scope, even if other components of the 1.56 @@ -1265,8 +1265,8 @@ 1.57 <p> For example, the <code>element.querySelector()</code> function defined 1.58 in <a href="#SELECTORS-API2" 1.59 rel=biblioentry>[SELECTORS-API2]<!--{{SELECTORS-API2}}--></a> allows the 1.60 - author to define a <a 1.61 - href="#scope-constrained"><i>scope-constrained</i></a> selector. 1.62 + author to define a <a href="#scope-filtered"><i>scope-filtered</i></a> 1.63 + selector. 1.64 1.65 <p> On the other hand, the <code>element.find()</code> function defined in 1.66 <a href="#SELECTORS-API2" 1.67 @@ -1810,10 +1810,10 @@ 1.68 by "-" (U+002D). This is primarily intended to allow language subcode 1.69 matches (e.g., the <code>hreflang</code> attribute on the <code>a</code> 1.70 element in HTML) as described in BCP 47 (<a href="#BCP47" 1.71 - rel=biblioentry>[BCP47]<!--{{BCP47}}--></a>) or its successor. For <a 1.72 - href="#lang-pseudo"><code>lang</code></a> (or <code>xml:lang</code>) 1.73 - language subcode matching, please see <a href="#lang-pseudo">the 1.74 - <code>:lang</code> pseudo-class</a>. 1.75 + rel=biblioentry>[BCP47]<!--{{BCP47}}--></a>) or its successor. For 1.76 + <code>lang</code> (or <code>xml:lang</code>) language subcode matching, 1.77 + please see <a href="#lang-pseudo">the <code>:lang</code> 1.78 + pseudo-class</a>. 1.79 </dl> 1.80 1.81 <p>Attribute values must be CSS <a 1.82 @@ -2003,13 +2003,13 @@ 1.83 appear in the document tree. Selectors should be designed so that they 1.84 work whether or not the default values are included in the document tree. 1.85 1.86 - <p>For example, a XML UA may, but is <a 1.87 - href="#negation-pseudo"><em>not</em></a> required to read an "external 1.88 - subset" of the DTD but <em>is</em> required to look for default attribute 1.89 - values in the document's "internal subset." (See, e.g., <a href="#XML10" 1.90 - rel=biblioentry>[XML10]<!--{{XML10}}--></a> for definitions of these 1.91 - subsets.) Depending on the UA, a default attribute value defined in the 1.92 - external subset of the DTD might or might not appear in the document tree. 1.93 + <p>For example, a XML UA may, but is <em>not</em> required to read an 1.94 + "external subset" of the DTD but <em>is</em> required to look for default 1.95 + attribute values in the document's "internal subset." (See, e.g., <a 1.96 + href="#XML10" rel=biblioentry>[XML10]<!--{{XML10}}--></a> for definitions 1.97 + of these subsets.) Depending on the UA, a default attribute value defined 1.98 + in the external subset of the DTD might or might not appear in the 1.99 + document tree. 1.100 1.101 <p>A UA that recognizes an XML namespace may, but is not required to use 1.102 its knowledge of that namespace to treat default attribute values as if 1.103 @@ -2577,8 +2577,7 @@ 1.104 innermost element, or ancestor of an element, that is currently being 1.105 displayed. 1.106 1.107 - <p>Its alternate form <a 1.108 - href="#current-pseudo"><code>:current()</code></a>, like <a 1.109 + <p>Its alternate form <code>:current()</code>, like <a 1.110 href="#matches-pseudo"><code>:matches()</code></a>, takes a list of <a 1.111 href="#compound"><i>compound selectors</i></a> as its argument: it 1.112 represents the <a href="#current-pseudo"><code>:current</code></a> element 1.113 @@ -2630,10 +2629,9 @@ 1.114 write selectors that represent an element based on its directionality as 1.115 determined by the document language. For example, in HTML <a 1.116 href="#HTML401" rel=biblioentry>[HTML401]<!--{{HTML401}}--></a>, the 1.117 - directionality of an element is determined by the <a 1.118 - href="#dir-pseudo"><code>dir</code></a> attribute. The <a 1.119 - href="#dir-pseudo"><code>:dir()</code></a> pseudo-class does not select 1.120 - based on stylistic states—for example, the CSS ‘<code 1.121 + directionality of an element is determined by the <code>dir</code> 1.122 + attribute. The <a href="#dir-pseudo"><code>:dir()</code></a> pseudo-class 1.123 + does not select based on stylistic states—for example, the CSS ‘<code 1.124 class=property>direction</code>’ property does not affect whether it 1.125 matches. 1.126 1.127 @@ -2653,9 +2651,9 @@ 1.128 attribute on the element, while the <code>:dir(C)</code> pseudo-class uses 1.129 the UAs knowledge of the document's semantics to perform the comparison. 1.130 For example, in HTML, the directionality of an element inherits so that a 1.131 - child without a <a href="#dir-pseudo"><code>dir</code></a> attribute will 1.132 - have the same directionality as its closest ancestor with a valid <a 1.133 - href="#dir-pseudo"><code>dir</code></a> attribute. As another example, <a 1.134 + child without a <code>dir</code> attribute will have the same 1.135 + directionality as its closest ancestor with a valid <code>dir</code> 1.136 + attribute. As another example, <a 1.137 href="http://www.w3.org/TR/html5/global-attributes.html#the-directionality">in 1.138 HTML5</a>, an element that matches <code>[dir=auto]</code> will match 1.139 either <code>:dir(ltr)</code> or <code>:dir(rtl)</code> depending on the 1.140 @@ -2682,10 +2680,10 @@ 1.141 document language. For example, in HTML <a href="#HTML401" 1.142 rel=biblioentry>[HTML401]<!--{{HTML401}}--></a>, the <a 1.143 href="#language"><i>language</i></a> is determined by a combination of the 1.144 - <a href="#lang-pseudo"><code>lang</code></a> attribute, information from 1.145 - <code>meta</code> elements, and possibly also the protocol (e.g. from HTTP 1.146 - headers). XML languages can use the <code>xml:lang</code> attribute to 1.147 - indicate language information for an element. 1.148 + <code>lang</code> attribute, information from <code>meta</code> elements, 1.149 + and possibly also the protocol (e.g. from HTTP headers). XML languages can 1.150 + use the <code>xml:lang</code> attribute to indicate language information 1.151 + for an element. 1.152 1.153 <p>The element's <i>language matches</i> a <i>language range</i> if the 1.154 element's <a href="#language"><i>language</i></a> (normalized to BCP 47
2.1 --- a/selectors4/Overview.src.html Fri Oct 12 15:30:09 2012 -0700 2.2 +++ b/selectors4/Overview.src.html Mon Oct 15 11:37:14 2012 -0700 2.3 @@ -611,7 +611,7 @@ 2.4 (The <code>:root</code> pseudo-class, however, 2.5 still only matches the actual root of the document.) 2.6 2.7 - <dt><dfn>scope-constrained</dfn> selectors 2.8 + <dt><dfn>scope-filtered</dfn> selectors 2.9 <dd> 2.10 With this method of scoping, a selector matches if 2.11 the <i>subject</i> of the selector is within the scope, 2.12 @@ -627,7 +627,7 @@ 2.13 <p> 2.14 For example, 2.15 the <code>element.querySelector()</code> function defined in [[SELECTORS-API2]] 2.16 - allows the author to define a <i>scope-constrained</i> selector. 2.17 + allows the author to define a <i>scope-filtered</i> selector. 2.18 2.19 <p> 2.20 On the other hand, the <code>element.find()</code> function defined in [[SELECTORS-API2]]