Closed
Bug 1944212
Opened 5 days ago
Closed 5 days ago
`mouseover` has wrong `relatedTarget` if the last `mouseover` target is removed
Categories
(Core :: DOM: Events, defect)
Core
DOM: Events
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: masayuki, Assigned: masayuki)
References
(Blocks 1 open bug)
Details
(Keywords: parity-chrome, webcompat:platform-bug)
No description provided.
|
Assignee | |
Comment 1•5 days ago
|
||
https://w3c.github.io/uievents/#event-type-mouseover
MouseEvent.relatedTarget : indicates the event target a pointing device is entering, if any.
I think it's typo, must be is leaving.
|
|
Assignee | |
Comment 2•5 days ago
|
||
Chrome sets the removed last mouseover target to relatedTarget, but it does not make sense for me because we need to keep maybe unnecessary nodes for long time.
|
||
Updated•5 days ago
|
Keywords: webcompat:platform-bug
|
|
Assignee | |
Comment 3•5 days ago
|
||
Okay, further investigation, I think that this is INVALID because the relatedTarget should be same as the deepest last mouseenter.
|
|
Assignee | |
Updated•5 days ago
|
Status: ASSIGNED → RESOLVED
Closed: 5 days ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•