1897220 - Content area and chrome remain active when context menu open on Windows

Status: NEW

(Core :: DOM: Core & HTML, defect)

Description

[Jeremy Swinarton]

Tested in Firefox 126 on Windows 11.

Steps to reproduce

1. Open any website with elements that change their appearance on hover
2. Mouse over the content area and right click to open a context menu
3. Move the mouse over any interactive element within the content area or in the browser chrome

Expected result

• All interactive elements are disabled while the context menu is open.

Actual result

• Hovering over elements in the chrome or content area produce state changes.

Additional notes

I also tested this on MacOS where the correct behaviour is exhibited. Also, on Windows, both Chrome and Edge disable all interactivity when context menus are open, which leads me to believe that there is a reasonable expectation that Windows apps will behave in this way.

Comment 1

[Alice0775 White]

At least on Windows, I think Firefox's behavior is correct in the following case.
Because, the fact that the hover state is displayed implies, in other words, that clicking on it will execute the default action.

Steps:

1. Open https://www.wikipedia.org/
2. Right click on blank area of the content
   --- Context menu will pop up as expected
3. Mouse hover over a any link / button of the content area
   --- Firefox: Hover state appears, It means, suggests that clicking will execute its default action.
   --- Chrome: No hover state appears, It means, suggests that clicking should do nothing.
4. Click on the element

Actual results:
Firefox execute default action of the element as expected.
Chrome, It didn't indicate hover state, so it shouldn't execute anything. Contrary to expectations, Chrome execute default action of the element without user feedback(i.e. hover state).

Comment 2

[Jeremy Swinarton]

I agree that the behaviour you describe in Chrome is not ideal, but I don't think that means this is functioning as expected. On Firefox / MacOS, if I open a context menu and then try to click on an interactive element on a page, Firefox does not execute anything, other than hiding the context menu. This is what I would expect to happen, and in my opinion this should be consistent behaviour across platforms.

Comment 3

[Sean Feng [:sefeng211]]

I agree this should be consistent. I'll try to figure something out.

Comment 4

[Sean Feng [:sefeng211]]

Clear my NI given I won't be able to work on this