[KDE/Wayland] userChrome.css transparent backgrounds render opaque in Firefox 150
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: mozilla.saturday612, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Steps to reproduce:
Environment:
OS: EndeavourOS (Arch-based)
Desktop: KDE Plasma 6, Wayland (KWin compositor)
GPU: NVIDIA RTX 4090, driver [your driver version]
Firefox: 150.0.1-1 (regression), 149.0-1 (working)
Steps to reproduce:
- Set widget.transparent-windows = true in about:config
- Set toolkit.legacyUserProfileCustomizations.stylesheets = true
- Add background: transparent !important to toolbar elements in userChrome.css
- Restart Firefox
Regression:
Works in Firefox 149.0-1, broken in 150.0.1-1. Downgrading to 149 immediately resolves it. Other userChrome rules (colors, layout changes) continue working in 150 — only transparency is affected.
Notes:
Firefox 150 release notes mention a Wayland compositor fix for Cosmic compositor. Suspected cause: opaque region reporting change breaking ARGB visual transparency on KWin.
Actual results:
Toolbar renders fully opaque, no transparency visible
Expected results:
Toolbar background is transparent, KWin blur composites through
Comment 1•4 months 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 2•4 months ago
|
||
Can you please use mozregression to find broken commit?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Use_Mozregression_tool
Thanks.
| Reporter | ||
Comment 3•4 months ago
|
||
(In reply to Martin Stránský [:stransky] (ni? me) from comment #2)
Can you please use mozregression to find broken commit?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Use_Mozregression_tool
Thanks.
Comment 4•1 month ago
|
||
Thanks, adding as regression but I don't think we support such setup so I guess it's WONTFIX. But let's see what Emilio says.
Comment 5•1 month ago
|
||
You need to make the <body> transparent now, see bug 2048355.
Description
•