This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24776 - mouseenter/mouseleave in 11.1/11.2 note
Summary: mouseenter/mouseleave in 11.1/11.2 note
Alias: None
Product: PointerEventsWG
Classification: Unclassified
Component: Pointer Events specification (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Jacob Rossi [MSFT]
QA Contact: Pointer Events Bugzilla list
Depends on:
Reported: 2014-02-22 20:47 UTC by Patrick H. Lauke
Modified: 2014-02-25 16:26 UTC (History)
1 user (show)

See Also:


Description Patrick H. Lauke 2014-02-22 20:47:48 UTC
Currently, the end of the last note on 11.1 and 11.2 reads

"And, the mouseover and mouseout events are never prevented (even if the pointer is down)."

Unless I'm mistaken, mouseover and mouseout can't be fired when the pointer is down anyway?

Also, should these notes also include mouseenter/mouseleave.

I'd suggest changing the wording in both cases to:

"And, the mouseover, mouseenter, mouseout and mouseleave events are never prevented."
Comment 1 Jacob Rossi [MSFT] 2014-02-25 07:39:42 UTC
I agree the notes should include enter/leave. Though, these events can be fired when the pointer is down (and do today in DOM3 Events).

I've added enter/leave to the note. If you still think there's an issue WRT when pointer is down, please reactivate and elaborate. Thanks!
Comment 2 Patrick H. Lauke 2014-02-25 08:32:51 UTC
Ah, forgot that mouseenter/mouseleave can happen when pointer is down. So in that situation, they CAN be prevented?

If it doesn't get too confusing, I wonder if - for completeness - the whole thing should then read along the lines of (removing the "And," at the start):

"mouseenter and mouseleave can only be prevented when the pointer is down, while mouseover and mouseout are never prevented."
Comment 3 Patrick H. Lauke 2014-02-25 16:26:45 UTC
Sorry, got confused it seems...