W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2012

[Bug 17626] mousemove event is really cancelable?

From: <bugzilla@jessica.w3.org>
Date: Wed, 12 Sep 2012 18:00:36 +0000
Message-Id: <E1TBrEq-0001XK-Av@jessica.w3.org>
To: www-dom@w3.org

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

           What    |Removed                     |Added
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WORKSFORME

--- Comment #9 from Travis Leithead [MSFT] <travil@microsoft.com> 2012-09-12 18:00:36 UTC ---
(In reply to comment #0)
> I'd like to confirm that is intentional change or a bug of the draft.
> In DOM2, mousemove event isn't cancelable, but the D3E spec draft defines it's
> cancelable.
> If that is intentional change, we will change the behavior on Gecko.
> https://bugzilla.mozilla.org/show_bug.cgi?id=704423
> See https://bugzilla.mozilla.org/show_bug.cgi?id=704423#c1 for the
> compatibility with browsers.
> I think that it should be cancelable. See
> http://lists.w3.org/Archives/Public/www-dom/2011OctDec/0253.html for the
> reason.

(In reply to comment #7)
> Excuse me, I don't understand what "WONTFIX" means for this bug.
> So, starting D3E, should the mousemove event be cancelable? I mean, should
> defaultPrevented be able to become true if preventDefault() is called?

To be clear--yes, mousemove should be cancelable and defaultPrevented should
become true when preventDefault() is called on this event.

There is no other tangible side-effect to cancelling this event that
implementers must support.

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 12 September 2012 18:00:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:19 UTC