Note

• Reproduced on a Surface 4 Pro device.

Found in

• Firefox 107.0b5

Affected versions

• Nightly 108.0a1
• Firefox 107.0b5
• Firefox 106.0.2
• Firefox 102.4.0esr

Tested platforms

• Affected platforms: Windows 10 x64

**Pre-requisites:

• Enable the Menu Bar and the Bookmarks Toolbar.

Steps to reproduce

1. Press and hold on the screen to open the context menu on the Bookmarks Toolbar, the Address Bar, the Tabs Bar, and the Menu Bar.

Expected result

• The specific context menus should be opened for all the mentioned Firefox bars.

Actual result

• The specific context menus are not opened. Please see the screen recording for more details.

Regression range

• This is not a regression, I could reproduce it all the way back on a Firefox 60 build.

Additional notes

• If the Title Bar is enabled, all the context menus are opened.

Does the "normal" webpage context menu work in this case?

(In reply to :Gijs (he/him) from comment #1)

Does the "normal" webpage context menu work in this case?

The webpage's context menu is not affected by the state of the Title Bar.

Molly is it easy for you to determine if this is an issue with our Win32 widget code or something in JS land? I guess it would require a touch device or a way to simulate native touch events...

So, I can reproduce this bug, but only for empty areas of any of those toolbars. If I tap and hold over a toolbar button, or a tab, or a bookmark, then I do get the context menu for that thing. I'm not sure how the widget layer would be accounting for that difference. I did have a quick look in there though, and I saw this somewhat worrying special case. I don't know where that APZ code that it's assuming will end up taking over actually is, so I can't easily verify that it really does.

Alright, well, over to win32 for triage then. :-)