[giow] (2) Define that :active works between mousedown and mouseup.

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=11343

git-svn-id: http://svn.whatwg.org/webapps@5881 340c8d12-0b0e-0410-8428-c7bf67bfef74

complete.html

@@ -52778,6 +52778,23 @@ <h4 id=pseudo-classes><span class=secno>4.14.2 </span>Pseudo-classes</h4>
     element received the <code title=event-keydown>keydown</code>
     event and the time the element received the <code title=event-keyup>keyup</code> event.</p>
 
+    <p>In addition, the <code title=selector-active><a href=#selector-active>:active</a></code>
+    pseudo-class must match any element that the user indicates using
+    a pointing device while that pointing device is in the "down"
+    state (e.g. for a mouse, between the time the mouse button is
+    pressed and the time it is depressed).</p>
+
+    <p class=note>This requirement is a <a href=#willful-violation>willful
+    violation</a> of the Selectors specification (which only allows
+    elements to match the <code title=selector-active><a href=#selector-active>:active</a></code>
+    pseudo-class when they are activated), motivated by a desire to be
+    compatible with legacy user agents. <a href=#refsSELECTORS>[SELECTORS]</a></p>
+
+    <p>In addition, the <code title=selector-active><a href=#selector-active>:active</a></code>
+    pseudo-class must match any element that has an ancestor that
+    matches the the <code title=selector-active><a href=#selector-active>:active</a></code>
+    pseudo-class.</p>
+
    </dd>
 
 

index

@@ -52761,6 +52761,23 @@ contradict people?
     element received the <code title=event-keydown>keydown</code>
     event and the time the element received the <code title=event-keyup>keyup</code> event.</p>
 
+    <p>In addition, the <code title=selector-active><a href=#selector-active>:active</a></code>
+    pseudo-class must match any element that the user indicates using
+    a pointing device while that pointing device is in the "down"
+    state (e.g. for a mouse, between the time the mouse button is
+    pressed and the time it is depressed).</p>
+
+    <p class=note>This requirement is a <a href=#willful-violation>willful
+    violation</a> of the Selectors specification (which only allows
+    elements to match the <code title=selector-active><a href=#selector-active>:active</a></code>
+    pseudo-class when they are activated), motivated by a desire to be
+    compatible with legacy user agents. <a href=#refsSELECTORS>[SELECTORS]</a></p>
+
+    <p>In addition, the <code title=selector-active><a href=#selector-active>:active</a></code>
+    pseudo-class must match any element that has an ancestor that
+    matches the the <code title=selector-active><a href=#selector-active>:active</a></code>
+    pseudo-class.</p>
+
    </dd>
 
 

source

@@ -59418,6 +59418,24 @@ contradict people?
     event and the time the element received the <code
     title="event-keyup">keyup</code> event.</p>
 
+    <p>In addition, the <code title="selector-active">:active</code>
+    pseudo-class must match any element that the user indicates using
+    a pointing device while that pointing device is in the "down"
+    state (e.g. for a mouse, between the time the mouse button is
+    pressed and the time it is depressed).</p>
+
+    <p class="note">This requirement is a <span>willful
+    violation</span> of the Selectors specification (which only allows
+    elements to match the <code title="selector-active">:active</code>
+    pseudo-class when they are activated), motivated by a desire to be
+    compatible with legacy user agents. <a
+    href="#refsSELECTORS">[SELECTORS]</a></p>
+
+    <p>In addition, the <code title="selector-active">:active</code>
+    pseudo-class must match any element that has an ancestor that
+    matches the the <code title="selector-active">:active</code>
+    pseudo-class.</p>
+
    </dd>