[selectors] Add selector profiles.

Author: tabatkins

selectors/Overview.html

@@ -181,6 +181,10 @@ <h2 class="no-num no-toc" id=contents>Table of Contents</h2>
 
    <li><a href="#overview"><span class=secno>2. </span> Selectors
     Overview</a>
+    <ul class=toc>
+     <li><a href="#profiles"><span class=secno>2.1. </span> "Fast" and
+      "Complete" Profiles</a>
+    </ul>
 
    <li><a href="#syntax"><span class=secno>3. </span> Selector Syntax and
     Structure</a>
@@ -1180,6 +1184,43 @@ <h2 id=overview><span class=secno>2. </span> Selectors Overview</h2>
    introduced in <a href="#CSS3UI"
    rel=biblioentry>[CSS3UI]<!--{{CSS3UI}}--></a>.
 
+  <h3 id=profiles><span class=secno>2.1. </span> "Fast" and "Complete"
+   Profiles</h3>
+
+  <p> Selectors are used in many different contexts, with wildly varying
+   performance characteristics. Some powerful selectors are unfortunately too
+   slow to realistically include in the more performance-sensitive contexts.
+   To accommodate this, two profiles of the Selectors spec are defined:
+
+  <dl>
+   <dt><dfn id=fast-profile>fast</dfn>
+
+   <dd> The ‘<a href="#fast-profile"><code class=css>fast</code></a>’
+    profile is appropriate for use in any context, including dynamic browser
+    CSS selector matching. It includes every selector defined in this
+    document, except for:
+    <ul>
+     <li>The "complex selector" variants of ‘<a
+      href="#matches-pseudo"><code class=css>:matches()</code></a>’ and
+      ‘<a href="#negation-pseudo"><code class=css>:not()</code></a>’.
+
+     <li>The <a href=idref-combinators>reference combinator</a>
+
+     <li>The <a href="#subject">subject indicator</a>
+    </ul>
+
+   <dt><dfn id=complete-profile>complete</dfn>
+
+   <dd> The ‘<a href="#complete-profile"><code
+    class=css>complete</code></a>’ profile is appropriate for contexts
+    which aren't extremely performance sensitive. For example,
+    implementations of the Selectors API specification <a
+    href="#SELECTORS-API"
+    rel=biblioentry>[SELECTORS-API]<!--{{SELECTORS-API}}--></a> should use
+    the ‘<a href="#complete-profile"><code class=css>complete</code></a>’
+    profile. It includes all of the selectors defined in this document.
+  </dl>
+
   <h2 id=syntax><span class=secno>3. </span> Selector Syntax and Structure</h2>
 
   <h3 id=structure><span class=secno>3.1. </span> Structure and Terminology</h3>
@@ -4431,6 +4472,15 @@ <h3 id=informative-references><span class=secno>20.2. </span> Informative
    </dd>
    <!---->
 
+   <dt id=SELECTORS-API>[SELECTORS-API]
+
+   <dd>Anne van Kesteren; Lachlan Hunt. <a
+    href="http://www.w3.org/TR/2013/REC-selectors-api-20130221/"><cite>Selectors
+    API Level 1.</cite></a> 21 February 2013. W3C Recommendation. URL: <a
+    href="http://www.w3.org/TR/2013/REC-selectors-api-20130221/">http://www.w3.org/TR/2013/REC-selectors-api-20130221/</a>
+   </dd>
+   <!---->
+
    <dt id=SELECTORS-API2>[SELECTORS-API2]
 
    <dd>Lachlan Hunt. <a

selectors/Overview.src.html

@@ -519,6 +519,38 @@ <h2 id="overview">
   <p class="note">Some Level 4 selectors (noted above as "3-UI") were
     introduced in [[CSS3UI]].
 
+<h3 id="profiles">
+"Fast" and "Complete" Profiles</h3>
+
+  <p>
+    Selectors are used in many different contexts,
+    with wildly varying performance characteristics.
+    Some powerful selectors are unfortunately too slow
+    to realistically include in the more performance-sensitive contexts.
+    To accommodate this, two profiles of the Selectors spec are defined:
+
+  <dl>
+    <dt><dfn id='fast-profile'>fast</dfn>
+    <dd>
+      The ''fast'' profile is appropriate for use in any context,
+      including dynamic browser CSS selector matching.
+      It includes every selector defined in this document,
+      except for:
+
+      <ul>
+        <li>The "complex selector" variants of '':matches()'' and '':not()''.
+        <li>The <a href="idref-combinators">reference combinator</a>
+        <li>The <a href="#subject">subject indicator</a>
+      </ul>
+
+    <dt><dfn id='complete-profile'>complete</dfn>
+    <dd>
+      The ''complete'' profile is appropriate for contexts which aren't extremely performance sensitive.
+      For example, implementations of the Selectors API specification [[SELECTORS-API]] should use the ''complete'' profile.
+      It includes all of the selectors defined in this document.
+  </dl>
+
+
 <h2 id="syntax">
 Selector Syntax and Structure</h2>