[selectors] Add an issue for ordering of pseudo-elements in selector match lists.

Author: tabatkins

selectors/Overview.bs

@@ -662,6 +662,11 @@ Evaluating a Selector</h3>
 	is the root element and all of its descendants,
 	ordered by a pre-order traversal.
 
+	Issue: The relative position of pseudo-elements in the <a>selector match list</a> is undefined.
+	There's not yet a context that exposes this information,
+	but we need to decide on something eventually,
+	before something <em>is</em> exposed.
+
 
 <h3 id='data-model'>
 Data Model</h3>

selectors/Overview.html

@@ -59,7 +59,7 @@
 </p>
   <h1 class="p-name no-ref" id=title>Selectors Level 4</h1>
   <h2 class="no-num no-toc no-ref heading settled heading" id=subtitle><span class=content>Editor’s Draft,
-    <span class=dt-updated><span class=value-title title=20140329>29 March 2014</span></span></span></h2>
+    <span class=dt-updated><span class=value-title title=20140403>3 April 2014</span></span></span></h2>
   <div data-fill-with=spec-metadata><dl><dt>This version:<dd><a class=u-url href=http://dev.w3.org/csswg/selectors>http://dev.w3.org/csswg/selectors</a><dt>Latest version:<dd><a href=http://www.w3.org/TR/selectors/>http://www.w3.org/TR/selectors/</a><dt>Editor’s Draft:<dd><a href=http://dev.w3.org/csswg/selectors>http://dev.w3.org/csswg/selectors</a><dt>Previous Versions:<dd><a href=http://www.w3.org/TR/2013/WD-selectors4-20130502/ rel=previous>http://www.w3.org/TR/2013/WD-selectors4-20130502/</a><dd><a href=http://www.w3.org/TR/2012/WD-selectors4-20120823/ rel=previous>http://www.w3.org/TR/2012/WD-selectors4-20120823/</a><dd><a href=http://www.w3.org/TR/2011/WD-selectors4-20110929/ rel=previous>http://www.w3.org/TR/2011/WD-selectors4-20110929/</a>
     <dt>Feedback:</dt>
         <dd><a href="mailto:www-style@w3.org?subject=%5Bselectors%5D%20feedback">www-style@w3.org</a>
@@ -890,6 +890,11 @@ <h3 class="heading settled heading" data-level=3.2 id=evaluating-selectors><span
 	is the root element and all of its descendants,
 	ordered by a pre-order traversal.
 
+<p class=issue id=issue-1bcc9de6><a class=self-link href=#issue-1bcc9de6></a>	 The relative position of pseudo-elements in the <a data-link-type=dfn href=#selector-match-list title="selector match list">selector match list</a> is undefined.
+	There’s not yet a context that exposes this information,
+	but we need to decide on something eventually,
+	before something <em>is</em> exposed.
+
 
 <h3 class="heading settled heading" data-level=3.3 id=data-model><span class=secno>3.3 </span><span class=content>
 Data Model</span><a class=self-link href=#data-model></a></h3>
@@ -3726,7 +3731,13 @@ <h2 class="no-num heading settled" id=issues-index><span class=content>Issues In
 		we should move them.
 
 
-<a href=#issue-cbdc0c66> ↵ </a></div><div class=issue>
+<a href=#issue-cbdc0c66> ↵ </a></div><div class=issue>	 The relative position of pseudo-elements in the <a data-link-type=dfn href=#selector-match-list title="selector match list">selector match list</a> is undefined.
+	There’s not yet a context that exposes this information,
+	but we need to decide on something eventually,
+	before something <em>is</em> exposed.
+
+
+<a href=#issue-1bcc9de6> ↵ </a></div><div class=issue>
 		The above algorithm is different from Selectors API: its step 2, which bailed if there were no :scope elements, has been removed.
 		This is because handling an explicitly empty list should return nothing;
 		if no :scope elements were given at all,