Closed
Bug 1284648
Opened 8 years ago
Closed 8 years ago
onclick fires onmouseout event uncalled
Categories
(Core :: DOM: Events, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1173716
People
(Reporter: joecs6, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0 Build ID: 20160623154057 Steps to reproduce: When using onclick and onmouseout on the same element onmouseout will be fired when a click is done: Fiddle http://jsfiddle.net/238Nz/8/ Actual results: onmouseout event will trigger uncalled. Expected results: no onmouseout trigger when only a click has been done.
Reporter | ||
Updated•8 years ago
|
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
Updated•8 years ago
|
Flags: needinfo?(bugs)
Updated•8 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 1•8 years ago
|
||
This is about us spinning event loop while showing alert(). Dup of an old bug.
Flags: needinfo?(bugs)
Comment 2•8 years ago
|
||
Thanks. I'll go with bug 1173716 but that itself has DUPEME ...
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 3•8 years ago
|
||
(In reply to Andrew Overholt [:overholt] from comment #2) > Thanks. I'll go with bug 1173716 but that itself has DUPEME ... > > *** This bug has been marked as a duplicate of bug 1173716 *** Hello, Andrew. Are you sure this a duplicate of bug 1173716? Because I've read it and it strikes no resemblance at all. The bug I posted here is about the mishandling of dom event onmouseout. Javascript it's a secondary tool to check the behavior of this event. Can you please check this one more time? Thanks.
Comment 4•8 years ago
|
||
(In reply to Joel Ramirez from comment #3) > Can you please check this one more time? Hi Joel, I was just going based on comment 1: (In reply to Olli Pettay [:smaug] from comment #1) > This is about us spinning event loop while showing alert(). Dup of an old > bug. Maybe Olli can enlighten us?
Flags: needinfo?(bugs)
Comment 5•8 years ago
|
||
if alert wasn't spinning the event loop on which the page runs, it shouldn't get the event before the alert has been closed. Another option is to move DelayedMouseEvent handling from PresShell to EventDispatcher... but the whole reason for DelayedMouseEvent is alert() and sync XHR which spin event loop.
Flags: needinfo?(bugs)
You need to log in
before you can comment on or make changes to this bug.
Description
•