2025243 - Right click context menu randomly selects items/tabs from the toolbar instead of the context menu

Status: RESOLVED DUPLICATE of bug 2026258

(Core :: Widget: Gtk, defect)

Description

[George]

Attachment: Screencast From 2026-03-23 08-34-48.mp4

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:148.0) Gecko/20100101 Firefox/148.0

Steps to reproduce:

• Open Firefox 148-150 (This happens on 3 different browsers: zen, firefox official nightly rpm and fedora's firefox rpm.)
• Go to any website (e.g. https://example.com or google.com).
• Right-click anywhere on the page content to open the context menu.
• Move the mouse over any context menu item (Inspect, Back, Reload, View Page Source, etc.).

Actual results:

The context menu never shows a highlight on hover.
Items on the toolbar (tabs, navigation buttons, bookmarks toolbar, etc.) randomly get highlighted or selected as if the mouse is over them.

Expected results:

Hovering over the context menu should highlight only the menu items (standard focus behaviour).
The toolbar should stay completely inactive while the context menu is open.

Comment 1

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'Firefox::Tabbed Browser' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[George]

This is still happening

Comment 3

[oliver]

I also have massive issues on Wayland with menu overlays since FF150.

• Context menus pop up in random places.
• Hamburger menu alternates from right edge of window to the left edge.

most of these overlay menus are barely unusable if you do manage to get to them, because they disappear as you move your cursor across them.

Comment 4

[oliver]

I have had to downgrade to FF149

                  -`                     oliver@athena
                 .o+`                    -------------
                `ooo/                    OS: Arch Linux - athena x86_64
               `+oooo:                   Host: MS-7D32 (1.0)
              `+oooooo:                  Kernel: Linux 6.19.14-arch1-1
              -+oooooo+:                 Uptime: 1 day, 12 hours, 9 mins
            `/:-:++oooo+:                Packages: 1048 (pacman)
           `/++++/+++++++:               Shell: bash 5.3.9
          `/++++++++++++++:              Display (DELL S2721DS): 2560x1440 in 27", 60 Hz [External]
         `/+++ooooooooooooo/`            Display (DELL S2721DS): 2560x1440 in 27", 60 Hz [External]
        ./ooosssso++osssssso+`           WM: niri 26.04 (Wayland)
       .oossssso-````/ossssss+`          Theme: Fusion [Qt]
      -osssssso.      :ssssssso.         Font: Noto Sans (12pt) [Qt]
     :osssssss/        osssso+++.        Cursor: default (24px)
    /ossssssss/        +ssssooo/-        Terminal: foot 1.26.1
  `/ossssso+/:-        -:/+osssso+-      Terminal Font: MesloLGS Nerd Font Mono (13pt)
 `+sso+:-`                 `.-/+oso:     CPU: 12th Gen Intel(R) Core(TM) i7-12700K (20) @ 5.00 GHz
`++:.                           `-/+/    GPU 1: AMD Radeon RX 570 Series [Discrete]
.`                                 `/    GPU 2: Intel UHD Graphics 770 @ 1.50 GHz [Integrated]
                                         Memory: 10.20 GiB / 31.06 GiB (33%)
                                         Swap: 13.50 MiB / 8.00 GiB (0%)
                                         Disk (/): 9.56 GiB / 87.26 GiB (11%) - ext4
                                         Disk (/home): 326.61 GiB / 819.15 GiB (40%) - ext4
                                         Local IP (enp4s0): 192.168.40.165/24
                                         Locale: en_GB.UTF-8

Comment 5

[Martin Stránský [:stransky] (ni? me)]

Oliver, is the bug new in Firefox 150.0 since you say you downgraded to 149.0? If so, can you please use mozregression to find the broken commit?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Use_Mozregression_tool
Thanks.

Comment 6

[oliver]

No need for the tool
As per my 2 comments above

149 => works
150 => broken

Comment 7

[oliver]

Sorry, I misunderstood that this tool allows you to pinpoint a more precise changeset.
I have tried to use it now, however, because the context menu (and hamburger menu) issue doesn't manifest itself until I have been using the browser for a little while, it will take a little while to use this bisecting tool to narrow things down.

First I am trying to establish repeatable path to the symptom, ideally.

Comment 8

[Martin Stránský [:stransky] (ni? me)]

There's know mutter bug while the focus is not transferred to popup if mouse button is hold. Is that the case? Does it work if you just click - open menu - release mouse button?
Thanks.

Comment 9

[oliver]

no that doesn't work either...

What makes my version of the issue difficult, is that it does not occur unitl the browser have been used for some time...
So doing the bisection is really hard, because I have not found a definitive path to reproduced it.

I have done clean profile and a range of nightlies - it's fine to find "bad", but "good" is always uncertain.

Comment 10

[oliver]

This niri issue tracks the symptoms I am having

and this FF commit fixes them (regression due to a change made for cosmic)

https://github.com/mozilla-firefox/firefox/commit/cf094fd8726a
https://bugzilla.mozilla.org/show_bug.cgi?id=2026258#c16

That fix has been uplifted to FF151 and I am running the beta7 of that now without problems.