We are overriding NSView mouseEntered/mouseExited methods to dispatch those, but they are not guaranteed to be called correctly when there are overlapping views, as is the case with WebViews and scrollers.
Created attachment 48824 [details] proposed patch
<rdar://problem/7417965>
Comment on attachment 48824 [details] proposed patch > + // This is observable via different order of events - in Firefox, attribute event listeners fires first I would change this to "event listeners specified as HTML attributes fire first". You *could* make an "attribute event listener" in JavaScript, and then it would fire in the order your script added it. r=me
All of <x onevent="..."> and x.onEvent = function () {...} and x.setAttribute("onevent", ...) are considered attribute event listeners in our code.
Committed <http://trac.webkit.org/changeset/54829>. > I would change this to "event listeners specified as HTML attributes fire > first". Done.