[Bug 8406] Stricter Specifications on Mouse Events Specifically primary, auxillary, and secondary default actions

https://www.w3.org/Bugs/Public/show_bug.cgi?id=8406

Travis Leithead [MSFT] <travil@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |travil@microsoft.com,
                   |                            |warcraftthreeft@sbcglobal.n
                   |                            |et

--- Comment #10 from Travis Leithead [MSFT] <travil@microsoft.com> 2012-03-15 23:59:36 UTC ---
Summary of the comments in this bug:

------------------------------------------------------
1 Note the [de facto] middle mouse button's default behavior (mouse-based
scroll)
2 Note the default action for the right mouse button (context menu)
3 Force mousedown messages before mouseup
4 Force mouseup messages when mouse leaves browser window
5 The specification should provide a value for no mouse button being depressed
6 If a new property (for button) is created, then event.button should be
deprecated.
------------------------------------------------------

This specification generally doesn't concern itself with the envirnment of the
user agent (e.g., whether it's windowed, full-screen, etc.). Thus, IMHO,
attempting to specify things that should/shouldn't happen when pointing devices
leave/enter the scope of the user agent is out of its purview. (items 3 & 4 --
though Comment 8 made it sound like you wanted to retract these
recommendations?)

I'm happy to add (non-normative) text describing the default actions of mouseup
with various button states, which seems useful for authors (Items 1 & 2)

Since the time this bug was filed, a new property "buttons" has been added that
uses the "IE" bitmask approach. I believe this satisfies item 5.
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-MouseEvent-buttons

Item 6: currently the spec does not deprecate either the "button" attribute or
the "buttons" attribute (which is new) on MouseEvent. Given the long history
and significant adoption of the "button" attribute, I don't believe it would be
appropriate to indicate that it is deprecated. In fact, I like that the
standard offers both options in this case. Depending on the specific scenario
you may choose one or the other.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 15 March 2012 23:59:42 UTC