- From: <bugzilla@jessica.w3.org>
- Date: Mon, 21 Oct 2013 21:05:21 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23240
Gary Kacmarcik <garykac@google.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #7 from Gary Kacmarcik <garykac@google.com> ---
Looking at the text in the spec some more, it contains the following passage
(which implies that click and dblclick should fire for all buttons):
The default action of the click event type varies based on the event target of
the event and the value of the MouseEvent.button or MouseEvent.buttons
attributes. Typical default actions of the click event type are as follows:
* Left click (MouseEvent.button value is 0, MouseEvent.buttons value is 1):
* If the event target has associated activation behavior, the default action
must be to execute that activation behavior (see Activation triggers and
behavior).
* If the event target is focusable, the default action must be to give that
element document focus.
* Right click (MouseEvent.button value is 1, MouseEvent.buttons value is 2):
* The default action must be to provide a context menu of options related to
that event target.
* Middle click (MouseEvent.button value is 2, MouseEvent.buttons value is 4):
* If the event target has associated activation behavior, the default action
must be to execute that activation behavior in an alternate fashion (such as
opening a link in a new tab or window).
* If the event target has no associated activation behavior, a user agent
may assign a custom default action such as an alternate scrolling or panning
mode.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 21 October 2013 21:05:23 UTC