Page MenuHomePhabricator

Bug 1977612 - feat(webgpu): allow `GPUBuffer`s in `GPUBindingResource` r=#webgpu-reviewers!
ClosedPublic

Authored by ErichDonGubler on Jul 17 2025, 3:59 AM.
Referenced Files
Unknown Object (File)
Thu, Apr 9, 10:53 AM
Unknown Object (File)
Thu, Apr 9, 9:32 AM
Unknown Object (File)
Thu, Apr 9, 6:13 AM
Unknown Object (File)
Tue, Apr 7, 9:59 AM
Unknown Object (File)
Fri, Apr 3, 5:39 AM
Unknown Object (File)
Oct 16 2025, 3:29 PM
Unknown Object (File)
Sep 12 2025, 9:15 PM
Unknown Object (File)
Sep 12 2025, 9:15 PM
Subscribers
None

Details

Summary

This change to upstream IDL happened at gpuweb#5193. Test coverage was added in gpuweb/cts#4390.

Event Timeline

phab-bot changed the visibility from "Custom Policy" to "Public (No Login Required)".
phab-bot changed the edit policy from "Custom Policy" to "Restricted Project (Project)".
phab-bot removed a project: secure-revision.

There are WPT tests that cover this at webgpu:api,validation,createBindGroup:buffer,resource_state:*, and I've confirmed that these tests work for most cases now. However, they have other blockers for completing successfully (for validation around buffers in the destroyed state). Even sadder, these tests for the destroyed state do not have any subtest granularity exposed, though internally the CTS does. So, relevant coverage still FAILs for us, because of other sins we'll eventually fix. Sigh. 🙁

This revision is now accepted and ready to land.Jul 17 2025, 9:38 AM