[Webkit-unassigned] [Bug 156971] Mouseleave fires on elements no longer in the DOM

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=156971

--- Comment #4 from David Kilzer (:ddkilzer) <ddkilzer at webkit.org> ---
(In reply to comment #3)
> (In reply to comment #1)
> > Correction:
> > 
> > See https://bugs.chromium.org/p/chromium/issues/detail?id=515921 for the
> > corresponding Chromium bug that was fixed late last year.
> 
> Blink commit where this is fixed:
> 
> <https://src.chromium.org/viewvc/blink?view=revision&revision=200656>

And the upstream commit log:

'''
Skipping mouseenter/over/out/leave on deleted nodes.

Both IE and FF skip firing of mouse transition events at deleted nodes,
with only IE doing it in a perfect manner by maintining the pairing of
entry/exit events. A crack in our code had been causing firing of these
events at a node after the node got deleted. This CL fixes the bug by
making chromium behave similar to FF. The perfect solution seems
non-trivial.

BUG=515921

Review URL: https://codereview.chromium.org/1288483003
'''

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160425/ac44c7f0/attachment.html>