WebGL with WebRender layer compositor on Wayland does not use overlay
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr140 | --- | unaffected |
| firefox148 | --- | unaffected |
| firefox149 | --- | unaffected |
| firefox150 | --- | fixed |
People
(Reporter: sotaro, Assigned: sotaro)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(2 files, 4 obsolete files)
|
14.36 KB,
patch
|
Details | Diff | Splinter Review | |
|
900 bytes,
patch
|
Details | Diff | Splinter Review |
Tested with the following with pref gfx.webrender.layer-compositor = true and pref gfx.webrender.compositor.force-enabled = true.
| Assignee | ||
Updated•8 months ago
|
| Assignee | ||
Comment 1•8 months ago
|
||
| Assignee | ||
Comment 2•8 months ago
|
||
From Attachment 9547452 [details] [diff], the WebGL image was not on picture surface.
Updated•8 months ago
|
| Assignee | ||
Updated•8 months ago
|
| Assignee | ||
Comment 3•8 months ago
|
||
| Assignee | ||
Comment 4•8 months ago
|
||
| Assignee | ||
Comment 5•8 months ago
|
||
| Assignee | ||
Comment 6•8 months ago
|
||
| Assignee | ||
Comment 7•8 months ago
|
||
| Assignee | ||
Comment 8•8 months ago
|
||
WebGL was rendered to offscreen surface since stacking context had a complex clip. It was decided in push_stacking_context().
| Assignee | ||
Comment 9•8 months ago
•
|
||
With Attachment 9548096 [details] [diff], the problem was addressed. Then rounded clip rect was added by ApplyOverflowClipping(). And the rounded clip rect was set to stacking context.
| Assignee | ||
Comment 10•8 months ago
|
||
Checked regression range with the following
./mach mozregression --good 2025-11-01 --pref gfx.webrender.debug.picture-borders:true -a https://webglsamples.org/aquarium/aquarium.html
| Assignee | ||
Updated•8 months ago
|
| Assignee | ||
Updated•8 months ago
|
| Assignee | ||
Comment 11•8 months ago
|
||
:emilio, can you look into this bug? Bug 2005854 fix seemed to cause this bug.
Comment 12•8 months ago
|
||
Seems like the same root cause as bug 2013682, right? If that could be looked into from the graphics team it'd be awesome. I can try but I'm a bit swamped with other things.
| Assignee | ||
Comment 13•8 months ago
|
||
OK, graphics team is going to look into this bug.
| Assignee | ||
Updated•8 months ago
|
| Assignee | ||
Comment 14•8 months ago
|
||
Confirmed that the patches in Bug 2013682 addressed the problem for me.
Updated•8 months ago
|
Updated•8 months ago
|
| Assignee | ||
Comment 15•7 months ago
|
||
Addressed by Bug 2013682 fix.
Updated•7 months ago
|
Comment 16•7 months ago
|
||
Think this was supposed to be marked fixed same as bug 2013682
Updated•7 months ago
|
Description
•