Bug 49297 - 'mouseup' directly following 'mousedown' but no 'click' event fired on a <button>
Summary: 'mouseup' directly following 'mousedown' but no 'click' event fired on a <but...
Status: RESOLVED DUPLICATE of bug 39620
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows XP
: P3 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-09 19:15 PST by Roy Goldman
Modified: 2011-08-15 14:19 PDT (History)
1 user (show)

See Also:


Attachments
ZIP file containing an HTML file demonstrating issue along with an AVI video of this issue (deleted)
2010-11-09 19:17 PST, Roy Goldman
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roy Goldman 2010-11-09 19:15:37 PST
As you can see in the attached html file (and a video demonstrating the issue), "click" is not firing reliably corresponding to matching "mousedown" and "onmouseup" events on a <button>.

More specifically, my understanding is that if I press the mouse button down over a <button> element (which fires 'mousedown'), and then release the mouse button while my pointer is still over that <button>, I should always get not only a 'mouseup' event on that element but also a 'click.'

However, in the attached html document, it's very easy to get a situation where the 'click' event does not fire, as evidenced by the Click counter not matching the Down and Up counters. Please see the attached video as well. The problem seems to be worse if the mouse pointer moves in between down and up, but in all cases the mouse pointer is staying over/within the <button>.

Is this by design? If so, what is the filter that prevents click from firing in some cases?

Reproduced in (and video from) webkit-r71499.
Comment 1 Roy Goldman 2010-11-09 19:17:39 PST
Created attachment 73451 [details]
ZIP file containing an HTML file demonstrating issue along with an AVI video of this issue
Comment 2 Ryosuke Niwa 2011-08-15 14:19:04 PDT

*** This bug has been marked as a duplicate of bug 39620 ***