186094 2018-05-30 07:43:48 -0700 mouseout and mouseleave should not be dispatched on removed DOM node 2019-02-06 21:54:24 -0800 1 1 1 Unclassified WebKit UI Events Safari 11 Unspecified Unspecified RESOLVED DUPLICATE 156971 InRadar P2 Normal --- 1 flackr webkit-unassigned cdumez dbates judeelliot2 rniwa webkit-bug-importer wenson_hsieh oldest_to_newest 1428423 0 flackr 2018-05-30 07:43:48 -0700 Visit http://output.jsbin.com/sekaqit Move the mouse over the gray hover me box The mouseenter listener removes the gray box According to https://www.w3.org/TR/uievents/#events-mouseevent-event-order: If the event target (e.g. the target element) is removed from the DOM during the mouse events sequence, the remaining events of the sequence MUST NOT be fired on that element. However, in Safari the mouseout and mouseleave events are fired. If you delay removing the DOM node, they are fired the next time the mouse is moved. If my reading of the spec is correct, Safari should not be dispatching mouseout and mouseleave on the removed node. 1428924 1 webkit-bug-importer 2018-05-31 11:31:06 -0700 <rdar://problem/40693039> 1497787 2 judeelliot2 2019-01-24 04:52:51 -0800 Most DOM events do bubble, however, there are a few exemptions. The mouse enter and mouse leave events don't bubble, however, mouseover and mouseout are the percolating partners. The concentration and obscure occasions don't bubble, however on standardizes focusing and focus out as foaming reciprocals. https://www.assignmentland.co.uk 1498120 3 rniwa 2019-01-24 19:51:46 -0800 WebKit's behavior matches that of Gecko but not Chrome. We'd have to figure out which one is more web compatible. The spec's text is probably irrelevant here (in that we should be changing the spec to whichever way that is more web compatible). 1503337 4 lforschler 2019-02-06 09:19:13 -0800 Mass move bugs into the DOM component. 1503623 5 rniwa 2019-02-06 21:05:32 -0800 *** This bug has been marked as a duplicate of bug 156971 ***