Version 2006021400 (1.0) A div in which Flash takes up the entire space will not receive an onmouseout event. However, if you leave some space inside the absolutely positioned div, it'll receive the event. Problem shown here: No absolute positioning - http://www.unleashthewonder.com/test/brian/onmouseout/test5/ Absolute positioning - http://www.unleashthewonder.com/test/brian/onmouseout/test1/ No problem here: http://www.unleashthewonder.com/test/brian/onmouseout/test4/ Two additional tests (both receive the event): no flash - http://www.unleashthewonder.com/test/brian/onmouseout/test2/ flash at bottom of page, but not inside DIV - http://www.unleashthewonder.com/test/brian/onmouseout/test3/

Trying to create a test on Bugzilla since I can't guarantee the tests will stay up.

Comment on attachment 217055 [details] test swf (ignore) oops

Test page, showing that no onmouseout happens in Camino. Works in Firefox on Mac. Flash 8.0.27 <offtopic>I noticed is that test 5 also doesn't work in Firefox on any system either (unless you hold the mouse and drag it over the object, which doesn't work in Camino), yet works in IE (w/o Eolas patch).</offtopic>

I figured out another piece of information: If you use addEventListener instead with setCapture set to true, it catches the event. So it only seems that it's blocked in the bubbling phase.

Simon, is this a dupe of bug 325558, or just related?

Certainly related. Does this happen in FF? Or on Windows?

This is now reproducible in trunk Firefox (2.x is fine), so moving to Cocoa widget.

Comment on attachment 279162 [details] [diff] [review] fix v1.0 It seems odd to use the NPEventType_AdjustCursorEvent event type for mouse-moved events ... but you're the one whose been doing the testing :-) And in any case there isn't a "mouse-moved" event type, so if you didn't use the adjustCursorEvent type you'd have to invent a new one. That quibble aside, the patch looks fine to me.

WebKit currently doesn't send native events to plugins for mouse moves, but according to Dave Hyatt they consider it a bug and are planning to do so. They plan to use adjustCursorEvent for the "what" field on the native event, which is exactly what my patch here has Gecko do. If you're wondering how Flash mouse tracking works in WebKit if they aren't sending the move events, it is because Flash has a workaround that updates the cursor position internally based on the null timer events.

landed on trunk