Context menu is too short if I right click the very top of the window
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: ator, Unassigned)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:137.0) Gecko/20100101 Firefox/137.0
Steps to reproduce:
Reproduced in Ubuntu/GNOME (Wayland) and Sway (Wayland). Could not reproduce in i3 (X11).
Right-click somewhere in the topmost layer of pixels of the window (NOT the window manager's titlebar).
Note: this is easy to notice in tiling window managers like Sway where the very top of the window is usually the very top of the screen, assuming that you don't have window borders or a topbar.
If the very top of the window is NOT the very top of the screen, you'll just have to keep shifting the mouse and right-clicking until you hit it!
Actual results:
About 75% of the time, the context menu is either slightly too short (an arrow covers the bottom item for no apparent reason) or much too short.
Expected results:
The context menu should be just tall enough - the way it is usually.
| Reporter | ||
Comment 1•1 year ago
|
||
Note: This is also the only row of pixels where you are unable to click on the Firefox top buttons (such as the hamburger). I'm pretty sure an update caused this a few months ago.
Comment 2•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 3•1 year ago
|
||
I didn't manage to reproduce this issue in Firefox 138.0.1 on Ubuntu 22.04 Wayland.
Could you please share a screenshot showing the issue reported, and confirm whether this still occurs when using a new profile or running Firefox in Safe Mode? Thank you.
Comment 4•1 year ago
|
||
Closing this as Resolved: Incomplete due to a lack of response from the reporter. If the issue still persists, please feel free to reopen the bug, and include the necessary details to help us investigate. Thank you.
| Reporter | ||
Comment 5•1 year ago
|
||
(In reply to Ina Popescu, Desktop QA from comment #3)
I didn't manage to reproduce this issue in Firefox 138.0.1 on Ubuntu 22.04 Wayland.
Could you please share a screenshot showing the issue reported, and confirm whether this still occurs when using a new profile or running Firefox in Safe Mode? Thank you.
Sorry, afraid I was too busy to do anything at the time and forgot 😅
It's much easier to reproduce in Sway (specifically, Regolith Ubuntu) than Ubuntu/GNOME, but still possible in both. It seems more likely to happen if you customise the toolbar, e.g. by removing the flexible spaces, but it's still much rarer in Ubuntu/GNOME (takes more attempts before you see it happen).
By the way, don't try in the areas that bring up the GNOME context menu on the second right-click, as it's harder to reproduce in that case, if not impossible.
Troubleshoot Mode and brand new profiles exhibit the same issue.
Comment 6•1 year ago
|
||
(In reply to Ator [:ator] from comment #5)
(In reply to Ina Popescu, Desktop QA from comment #3)
I didn't manage to reproduce this issue in Firefox 138.0.1 on Ubuntu 22.04 Wayland.
Could you please share a screenshot showing the issue reported, and confirm whether this still occurs when using a new profile or running Firefox in Safe Mode? Thank you.Sorry, afraid I was too busy to do anything at the time and forgot 😅
It's much easier to reproduce in Sway (specifically, Regolith Ubuntu) than Ubuntu/GNOME, but still possible in both. It seems more likely to happen if you customise the toolbar, e.g. by removing the flexible spaces, but it's still much rarer in Ubuntu/GNOME (takes more attempts before you see it happen).
By the way, don't try in the areas that bring up the GNOME context menu on the second right-click, as it's harder to reproduce in that case, if not impossible.
Troubleshoot Mode and brand new profiles exhibit the same issue.
Thanks for providing the details. I’m not able to reproduce this on Ubuntu Wayland, maybe I'm misunderstanding something. Could you send a quick screen recording showing the context menu appearing too short when right-clicking the very top of the window?
| Reporter | ||
Comment 7•11 months ago
|
||
Can no longer reproduce in the desktop environment I use (Sway (Wayland)), where it used to happen all the time 🙂
Thank goodness, because I forgot about making that screen recording 😅
| Reporter | ||
Comment 8•11 months ago
|
||
Could someone mark this COMPLETE please?
| Reporter | ||
Comment 9•11 months ago
|
||
Never mind... now an even stranger version is occurring, just more rarely.
The only pattern I've noticed so far is it only happens if I haven't used that context menu for about a minute.
| Reporter | ||
Comment 10•11 months ago
|
||
The context menu is tiny in width and height, requiring scrolling, and its submenu has inconsistent positioning.
Updated•11 months ago
|
Comment 11•11 months ago
|
||
Okay, please run on terminal with MOZ_LOG="Widget:5 WidgetPopup:5" env variables and attach the log here.
Thanks.
| Reporter | ||
Comment 12•10 months ago
|
||
:stransky I can't seem reproduce it on my laptop alone; only when I have my monitor attached. (Note: using Wayland via the sway tiling window manager)
I have added the log below. No lines get added when the bug occurs; I've tested this twice.
[2] Sandbox: CanCreateUserNamespace() clone() failure: EPERM
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/intel-vaapi-driver/radeonsi_drv_video.so
libva info: Trying to open /usr/lib/x86_64-linux-gnu/GL/lib/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
Comment 13•10 months ago
|
||
Strange. Can you try as:
MOZ_LOG="Widget:5,WidgetPopup:5" firefox
Updated•10 months ago
|
Comment 14•5 months ago
|
||
(In reply to Martin Stránský [:stransky] (ni? me) from comment #13)
Strange. Can you try as:
MOZ_LOG="Widget:5,WidgetPopup:5" firefox
Ator?
Comment 15•5 months ago
|
||
Looks like Sway bug, may be already fixed.
Updated•5 months ago
|
| Reporter | ||
Comment 16•5 months ago
|
||
Sorry both, I meant to reply but reproducing it was always time-consuming and life has been hectic! I haven't noticed it recently though, so maybe it's fixed :)
Description
•