W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2011

[DOM3 Events] mousemove event is cancelable in D3E, but is this intentional?

From: Masayuki Nakano <masayuki@d-toybox.com>
Date: Thu, 22 Dec 2011 16:18:04 +0900
Message-ID: <4EF2D9AC.4000708@d-toybox.com>
To: "www-dom@w3.org" <www-dom@w3.org>
Hello,

mousemove event is now cancelable in D3E draft. I'd like to confirm if 
it was changed from DOM2 intentionally since I cannot find any 
discussion about this change.

I think that it should be cancelable for preventing default actions of 
web browser. E.g., web developers can prevent to change selection range 
by mousemove. And it may be useful for some web applications which 
implement complex UI parts. E.g., web application create <A><B></B></A>, 
and both <A> and <B> handle mousemove event but <A> doesn't need to 
handle after <B>. Then, it's useful if mousemove is cancelable.

IE9 and Opera support preventDefault() of mousemove event. (I mean the 
defaultPrevented returns true after calling preventDefault()).

WebKit and Gecko don't do so yet.

Although, both IE9 and Opera cannot prevent to change :hover state and 
to change selection by mouse.

I'm working on about this issue of Gecko.
https://bugzilla.mozilla.org/show_bug.cgi?id=704423

-- 
Masayuki Nakano <masayuki@d-toybox.com>
Manager, Internationalization, Mozilla Japan.
Received on Thursday, 22 December 2011 07:18:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:08 GMT