[wayland] Context menus sometimes briefly show/flash underlying window when first drawn
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr128 | --- | unaffected |
| firefox-esr140 | --- | unaffected |
| firefox141 | --- | unaffected |
| firefox142 | --- | wontfix |
| firefox143 | --- | wontfix |
| firefox144 | --- | fixed |
People
(Reporter: ke5trel, Assigned: stransky)
References
(Depends on 1 open bug, Blocks 2 open bugs, Regression)
Details
(Keywords: regression)
Attachments
(1 file, 4 external files, 1 obsolete file)
|
92.44 KB,
image/png
|
Details |
STR:
- Start latest Nightly 143.0a1 with
MOZ_ENABLE_WAYLAND=1on Ubuntu 25.04. - Enable the Dark theme.
- Unmaximize the window.
- Visit a website with a light background.
- Create a new unmaximized window (overlapping existing window).
- Show the context menu by right-clicking the bookmarks toolbar.
- Show the context menu by right-clicking the tab bar.
- Repeat steps 6-7 in different areas.
Expected:
Context menu never shows anything beneath window.
Actual:
Context menu sometimes briefly shows underlying window when created (flashes light color), especially when menu dimensions change.
Only happens when both windows are unmaximized.
Does not happen with MOZ_ENABLE_WAYLAND=0.
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=908e181f8330ec6743d1c626b38023270a98be38&tochange=ad16af6bf6aa841019c39de701518f0b5777f9b3
Regressed by Bug 1967114.
Comment 1•1 year ago
|
||
:emilio, since you are the author of the regressor, bug 1967114, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Comment 2•1 year ago
|
||
Seems like a mutter bug? Not sure how you'd get that rendering otherwise. Does it happen on other DEs like KDE?
| Assignee | ||
Comment 3•1 year ago
|
||
Kestrel, please attach your about:support page.
Thanks.
- Happens with GNOME 46.0 and 48.0 but not KDE (Kubuntu 25.04).
- Happens with snap (Mesa 24.2.8.0), tarball (Mesa 25.0.7.0) and flatpak (Mesa 25.1.3.0).
- Also occurs with Ubuntu 24.04.2 LTS (Mesa 24.2.8.0) on different hardware.
- Happens with HW-WR and SW-WR.
- 100% scaling on single display.
- Clean profile with stock settings.
Is there anything specific in about:support you are interested in?
| Assignee | ||
Comment 5•1 year ago
|
||
No, that's fine, thanks.
| Assignee | ||
Updated•1 year ago
|
Comment 6•1 year ago
|
||
:stransky is this going to be targeting 142?
| Assignee | ||
Comment 7•1 year ago
|
||
(In reply to Dianna Smith [:diannaS] from comment #6)
:stransky is this going to be targeting 142?
No, I have no idea what's going on here.
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 8•1 year ago
|
||
If Bug 1967114 is the regression here it may be caused by improved opaque region handling. We may set opaque region to popup before we actually paint its content so we (correctly) may see any background under the popup before we paint it.
| Assignee | ||
Comment 9•1 year ago
|
||
I guess debug build may show it.
| Assignee | ||
Comment 10•1 year ago
|
||
I can reproduce that on debug build. The underlying Firefox window has to contain any image to make the effect visible.
| Assignee | ||
Comment 11•1 year ago
|
||
Also it's reproducible on 50% cases and perhaps depends on popup content - it's more likely when new popup is opened, repeated popup open doesn't shown it.
| Assignee | ||
Comment 12•1 year ago
|
||
| Assignee | ||
Comment 13•1 year ago
|
||
| Assignee | ||
Comment 14•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 15•1 year ago
|
||
The opaque region change takes action even before we have window content painted, so deffer the change
until there's anything painted in the window and we get frame callback for it.
Updated•1 year ago
|
| Assignee | ||
Comment 16•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
Comment 17•1 year ago
|
||
Comment 18•1 year ago
|
||
Comment 19•1 year ago
|
||
Backed out for causing build bustages
- Backout link
- Push with failures
- Failure Log
- Failure line: /builds/worker/workspace/obj-build/dist/include/mozilla/RefPtr.h:49:38: error: member access into incomplete type '_GdkWindow'
Comment 21•1 year ago
|
||
Comment 22•1 year ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/9d149e211266
https://hg.mozilla.org/mozilla-central/rev/8945d6de2c24
https://hg.mozilla.org/mozilla-central/rev/66bd4fee13bb
https://hg.mozilla.org/mozilla-central/rev/a582687dd82d
Comment 23•1 year ago
|
||
The patch landed in nightly and beta is affected.
:stransky, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox143towontfix.
For more information, please visit BugBot documentation.
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Description
•