← back to v146 · webgpu-transient-attachments
conformance · v146
v146 · webgpu-transient-attachments — conformance probe
6 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
gputextureusage-namespace-exists |
GPUTextureUsage is exposed as a namespace object on the global scope. | exists | … | |
gputextureusage-transient-attachment-bit |
GPUTextureUsage.TRANSIENT_ATTACHMENT is exposed as a numeric bitflag. | script | … | |
transient-attachment-distinct-from-render-attachment |
TRANSIENT_ATTACHMENT is a distinct bit from RENDER_ATTACHMENT (they can be ORed together). | script | … | |
transient-attachment-non-zero |
The TRANSIENT_ATTACHMENT bit is non-zero so it can be ORed into a usage mask. | script | … | |
createtexture-accepts-transient-attachment-bit |
GPUDevice.createTexture accepts the TRANSIENT_ATTACHMENT bit in the usage field without throwing for a small valid descriptor. | script | … | |
transient-attachment-rejects-with-copy-bits |
Spec: a texture with TRANSIENT_ATTACHMENT must not also be COPY_SRC/COPY_DST — combining them throws a validation error. | script | … |