11343 2010-11-19 02:15:33 +0000 Browsers allow *any* element to match :active between a mousedown on it and the subsequent mouseup. The definition of :active should change to match this behavior. 2011-08-04 05:02:25 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#pseudo-classes P3 normal --- 1 contributor ian dbaron fantasai.bugs ian jackalmage mike mounir public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 42625 0 contributor 2010-11-19 02:15:33 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/links.html Section: http://www.whatwg.org/specs/web-apps/current-work/#pseudo-classes Comment: Browsers allow *any* element to match :active between a mousedown on it and the subsequent mouseup. The definition of :active should change to match this behavior. Posted from: 216.239.45.4 42627 1 jackalmage 2010-11-19 02:22:45 +0000 Test case illustrating the behavior: data:text/html,<!doctype html><style>*:active { color: red; }</style><div>foo<br>bar</div> The <div> is not on the list of explicit elements with special :active behavior, nor is it "specially focusable", but it will still turn red when you click on it. 42629 2 mike 2010-11-19 03:52:57 +0000 *** Bug 11344 has been marked as a duplicate of this bug. *** 42631 3 fantasai.bugs 2010-11-19 08:11:08 +0000 FWIW, it's called :active, not :onmousedown. I disagree with this change unless it's a significant web-compat issue. (Note also that any pages relying on this behavior are not keyboard accessible, since the <div> under question is not focusable.) 43686 4 ian 2010-12-31 07:10:05 +0000 See also: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-December/thread.html#29530 Unless browsers change, the spec is going to match the general direction of implementations. 45421 5 ian 2011-02-12 00:33:08 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. Would be nice if Selectors would match reality on this too. In the meantime, I've added a "willful violation" note here and specced what Tab suggests. 45422 6 contributor 2011-02-12 00:33:30 +0000 Checked in as WHATWG revision r5881. Check-in comment: Define that :active works between mousedown and mouseup. http://html5.org/tools/web-apps-tracker?from=5880&to=5881 52540 7 mike 2011-08-04 05:02:25 +0000 mass-moved component to LC1