OffscreenCanvas presentation via WebGPU is probably broken
Categories
(Core :: Graphics: WebGPU, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox124 | --- | unaffected |
firefox125 | --- | disabled |
firefox126 | --- | disabled |
firefox127 | --- | disabled |
firefox128 | --- | disabled |
People
(Reporter: jimb, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
After some discussion, :erichdongubler and I are pretty sure the fix for bug 1883810 is wrong. I had misunderstood how OffscreenCanvas
was meant to behave. Completion of rendering on a texture returned by calling getCurrentTexture
on a GPUCanvasContext
obtained from an OffscreenCanvas
should indeed provoke presentation in some way, whereas 1883810 simply cuts them out of the presentation flow altogether.
The correct fix for bug 1883810 is probably to treat validation of the canvas size differently.
Updated•1 year ago
|
Reporter | ||
Updated•11 months ago
|
Updated•11 months ago
|
Comment 1•11 months ago
|
||
Set release status flags based on info from the regressing bug 1883810
:ErichDonGubler, since you are the author of the regressor, bug 1883810, could you take a look?
For more information, please visit BugBot documentation.
Updated•11 months ago
|
Reporter | ||
Comment 2•11 months ago
|
||
Erich is already aware of the issue, and this has been prioritized amongst WebGPU's other priorities.
Updated•11 months ago
|
Comment 3•11 months ago
|
||
Set release status flags based on info from the regressing bug 1883810
Updated•9 months ago
|
Updated•9 months ago
|
Updated•3 months ago
|
Description
•