Closed Bug 1885402 Opened 2 years ago Closed 1 year ago

OffscreenCanvas presentation via WebGPU is probably broken

Categories

(Core :: Graphics: WebGPU, defect, P2)

Product:
Core
Component:
Graphics: WebGPU
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1936734
Tracking Flags:
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.

Summary: OffscreenCanvas presentation is probably broken → OffscreenCanvas presentation via WebGPU is probably broken
Blocks: webgpu-triage
Keywords: regression
Regressed by: 1883810
No longer regressions: 1883810

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.

status-firefox124: --- → unaffected
status-firefox125: --- → affected
status-firefox126: --- → affected
status-firefox-esr115: --- → unaffected
Flags: needinfo?(egubler)

Erich is already aware of the issue, and this has been prioritized amongst WebGPU's other priorities.

Flags: needinfo?(egubler)

Set release status flags based on info from the regressing bug 1883810

status-firefox127: --- → affected
Status: NEW → RESOLVED
Closed: 1 year ago
Duplicate of bug: 1936734
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.