Very difficult to click on extensions dropdown menu items
Categories
(Core :: Widget: Gtk, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | unaffected |
| firefox107 | --- | unaffected |
| firefox108 | --- | fixed |
| firefox109 | --- | fixed |
People
(Reporter: gerard-majax, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(1 file)
|
2.43 MB,
video/webm
|
Details |
STR:
- Ensure to have recent build id, e.g. 20221112215806
- (ubuntu 22.10 uptodate? wayland?)
- Click an extension in the extensions panels (e.g., Multi-Account Containers, Bitwarden)
- Try to click an item in the menu (e.g., container name in Multi-Account Containers, or credententials in Bitwarden)
Expected:
I can click and the corresponding action happens (opening a new container tab or filling credentials)
Actual:
Nothing happens. If the menu item is over content that can receive a click event, it will propagate to content (e.g., bugzilla search list column header will receive and change sorting)
Switching ui.panelAnimations = 0 avoids the issue.
Comment 1•3 years ago
|
||
What compositor / etc are you using? Ubuntu presumably uses Mutter? And if so which version?
| Reporter | ||
Comment 2•3 years ago
|
||
$ dpkg --list|grep -E "libwayland|libmutter"
ii libmutter-11-0:amd64 43.0-1ubuntu4 amd64 window manager library from the Mutter window manager
ii libwayland-bin 1.21.0-1 amd64 wayland compositor infrastructure - binary utilities
ii libwayland-client0:amd64 1.21.0-1 amd64 wayland compositor infrastructure - client library
ii libwayland-cursor0:amd64 1.21.0-1 amd64 wayland compositor infrastructure - cursor library
ii libwayland-dev:amd64 1.21.0-1 amd64 wayland compositor infrastructure - development files
ii libwayland-egl1:amd64 1.21.0-1 amd64 wayland compositor infrastructure - EGL library
ii libwayland-server0:amd64 1.21.0-1 amd64 wayland compositor infrastructure - server library
Updated•3 years ago
|
Updated•3 years ago
|
Fedora 37 GNOME
Last good revision: 3924518919682eae3ae92f9c6da486b361e4ea80
First bad revision: 8e9534dd0451f24dd851905af796475b61aa8e44
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=3924518919682eae3ae92f9c6da486b361e4ea80&tochange=8e9534dd0451f24dd851905af796475b61aa8e44
Comment 4•3 years ago
|
||
I do see that too - an extension popup is not visible.
Comment 5•3 years ago
|
||
Set release status flags based on info from the regressing bug 1799901
Comment 6•3 years ago
|
||
The missing popups use HW WebRender (they are remote popups). We may fail to finish it's rendering somehow. I also wonder if Vsync is involved here and if switch to SW Vsync helps.
Updated•3 years ago
|
Updated•3 years ago
|
Description
•