W3C home > Mailing lists > Public > public-webapi@w3.org > March 2006

ISSUE-54: non-issue regarding MouseEvent.button

From: Web APIs Issue Tracker <dean+cgi@w3.org>
Date: Mon, 27 Mar 2006 13:05:24 +0000 (GMT)
To: public-webapi@w3.org
Message-Id: <20060327130524.52A98BDA7@w3c4.w3.org>


ISSUE-54: non-issue regarding MouseEvent.button

http://www.w3.org/2005/06/tracker/webapi/issues/54

Raised by: Anne van Kesteren
On product: DOM 3 Events

Suggestion resolution: leave it like it is (and perhaps chase down the guy who
did not think of the fancy bitmask solution).

"Testcases":
 http://annevankesteren.nl/test/dom/events/dump/001.svg
 http://annevankesteren.nl/test/dom/events/dump/002.htm

With help from Maciej and Björn it seems that Batic, Opera, Mozilla, Safari and
ASV all do it like the W3C specified. That is, 0: left click, 1: middle click,
2: right click. Although it's not always reported as click for every button...

Internet Explorer is the only browser that differs that has implemented
MouseEvent.button as a bitmask. 1: left click, 2: right click, 4: middle click.
And of course, 3: left + right click, 5: left + middle click, 6: right + middle
click and 7: left + right + middle click. (It has been reported that this
bitmasking behavior does not always work...)
Received on Monday, 27 March 2006 13:05:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:54 GMT