533608 - Should receive MouseLeave event when mouse moves from plug onto HTML

Status: RESOLVED WONTFIX

(Core Graveyard :: Plug-ins, defect, P3)

Description

[Andy Rivas]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)

If we have a windowless Silverlight (SL) plug in, and some HTML content overlaps the plug in, then different browsers behave differently when the cursor moves over the area where the HTML content overlaps the plug in.

FF 3.5 and Chrome3 on Windows: We never receive MOUSE_LEAVE message when the mouse cursor moves from the plugin into the HTML hyperlink, so the SL button stays in MouseOver state forever, but the mouse cursor is changed to Hand (which is correct, since Hand is the default cursor for hyperlink).

FF on Mac: Similar to FF/Chrome on Windows with one distinction – we do receive the MOUSE_LEAVE message, but we only receive it when the mouse cursor exits plugin bounds (unlike IE, where we receive the MOUSE_LEAVE as soon as the cursor enters the HTML content). So the SL button stays in MouseOver state and mouse cursor is displayed as hand, as long as we are over HTML content overlapping the plugin area. But as soon as the cursor exits the plugin area, the button changes to regular, non-MouseOver state and mouse cursor is reset to arrow (which is incorrect, since it is still over the hyperlink).

Reproducible: Always

Steps to Reproduce:
Config: Firefox on Mac and Windows

1. Open attached repro app
2. Move mouse over the button and into the HTML hyperlink


Actual Results:  
Actual Results:
SL button stays in MouseOver state but the mouse cursor changed to the hand

Expected Results:  
Expected Results:
SL button state changes and the mouse cursors changes to the hand

Comment 1

[Andy Rivas]

Attachment: Zip file containing the sample application

Comment 2

[Andy Rivas]

Adding one comment to the repro steps.

1. Open the attached repro app (Repro.html)

Comment 3

[Andy Rivas]

Has anyone looked at this?

Comment 4

[Andy Rivas]

Ping.  Has anyone looked as this?  Run the attached app an you can see the behavior.

Thanks

Comment 5

[BMO Automation]

Resolving as wont fix, plugin support deprecated in Firefox 85.