WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED DUPLICATE of
bug 39620
49297
'mouseup' directly following 'mousedown' but no 'click' event fired on a <button>
https://bugs.webkit.org/show_bug.cgi?id=49297
Summary
'mouseup' directly following 'mousedown' but no 'click' event fired on a <but...
Roy Goldman
Reported
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
.
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
View All
Add attachment
proposed patch, testcase, etc.
Roy Goldman
Comment 1
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
Ryosuke Niwa
Comment 2
2011-08-15 14:19:04 PDT
*** This bug has been marked as a duplicate of
bug 39620
***
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug