Bug 26401

Summary:

mousemove event fired on click, even though the mouse does not move

Product:

WebKit

Reporter:

simon <simon.brent>

Component:

UI Events

Assignee:

Nobody <webkit-unassigned>

Status:

NEW

Severity:

Normal

CC:

ap, kangax, me, odai640680odai, rniwa, sam

Priority:

Version:

528+ (Nightly build)

Hardware:

OS:

Windows XP

URL:

http://jsbin.com/iwige

Attachments:

Description	Flags
DRT test	none

simon

Reported 2009-06-15 03:44:53 PDT

When you make a mouse click, the following events are fired (in order): mousedown, mouseup, click, mousemove even if the mouse has not moved. Similarly, if you DO move the mouse between mousedown and mouseup, an extra mousemove event is fired after mouseup, so the events fired are mousedown, mousemove, mouseup, mousemove

Attachments
DRT test (408 bytes, text/html) 2011-08-15 10:31 PDT, Ryosuke Niwa	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Michaël Villar

Comment 1 2010-06-19 08:22:43 PDT

I have a similar bug. I illustrated it here : http://michaelvillar.com/tmp/click_mousemove_bdc4.html The mousemove event is fired after a click even if the mouse doesn't move.

Michaël Villar

Comment 2 2010-06-19 08:32:15 PDT

It appears it's working as expected in Chrome 5.0.375.70. The problem still exists in Safari 5 and the latest Webkit nightly r61351

Ryosuke Niwa

Comment 3 2011-08-15 10:30:21 PDT

The bug appears to be in (void)mouseUp:(NSEvent *)event in WebHTMLView.mm. It calls [self _updateMouseoverWithFakeEvent], which in turn fires mousemove event.

Ryosuke Niwa

Comment 4 2011-08-15 10:31:10 PDT

Created attachment 103923 [details] DRT test

Alexey Proskuryakov

Comment 5 2011-08-15 10:37:59 PDT