context menu on link in page viewport's far lower-right shouldn't self-select unwanted command
Categories
(Toolkit :: UI Widgets, defect)
Tracking
()
People
(Reporter: Nick_Levinson, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0
Steps to reproduce:
-
Go to a URL that shows a link in the far lower right corner of the viepwort.
-
Context-click (usually right-click) the link. The menu should pop up upward and to the left.
-
Try to select Open Link in New Tab. That command is at the top of the context menu.
Actual results:
You can't do step 3. Instead, because the pointer is resting on the last command, when I let go of the touchpad button (like a mouse button), that command executes immediately. Since that command happens to be Inspect Element, the Inspect Element window opens and that's big enough that it hides the link and I have to try again.
Expected results:
No execution until a command is deliberately chosen, so the user can select another command first. The menu should stay visible until then.
Additional info:
Version 79.0 (64-bit). Platformm: x86_64. OS: Fedora 32 Linux kept evergreen.
Examples: nytimes.com nypost.com reddit.com
If the menu were elsewhere in the viewport, when I let go of the touchpad button, the menu would stay in place and wait for me to select a command or dismiss the menu.
A kludge or workaround, when the menu is up and to the left of the cursor, is to hold the laptop's context button down (so it doesn't execute the bottom command) and use a finger on the touchpad to move the pointer up through the commands.
|
||
Comment 1•5 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
|
||
Comment 2•5 years ago
|
||
I suspect this is something that the XULPopupManager might need to deal with. I believe this is the right component.
|
||
Comment 3•5 years ago
|
||
This only seems to happen when the pointer is in very specific locations near the lower right of the screen. It actually happens in other applications as well, but GTK menus seem to delay a second before highlighting the menu item to mitigate this somewhat.
A possible fix is to modify the setting and checking of nsMenuFrame::gMenuJustOpenedOrClosed to handle context menus and not just those inside a <menu>.
Description
•