Contact emails
cwa...@google.com
Explainer
https://gpuweb.github.io/gpuweb/#dom-gpufeaturename-texture-compression-unaligned
Specification
https://gpuweb.github.io/gpuweb/#dom-gpufeaturename-texture-compression-unaligned
Summary
Compressed texture (using the BC, ETC or ASTC formats) in unextended WebGPU must have a size that's a multiple of the block size (4x4 or up to 12x12). This is very constraining when compressing arbitrary images as a resizing step must happen which looses high-frequency information.
Most hardware supports compressed textures with partial blocks at the border such that the textures can have any size, removing this issue.
Blink component
Blink>WebGPU
Web Feature ID
webgpu
Motivation
Compressed texture (using the BC, ETC or ASTC formats) in unextended WebGPU must have a size that's a multiple of the block size (4x4 or up to 12x12). This is very constraining when compressing arbitrary images as a resizing step must happen which looses high-frequency information.
Most hardware supports compressed textures with partial blocks at the border such that the textures can have any size, removing this issue.
Initial public proposal
https://github.com/gpuweb/gpuweb/issues/2006
TAG review
No information provided
TAG review status
Not applicable
Goals for experimentation
None
Risks
Debuggability
No information provided
Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
Yes
All platforms have support, where hardware support is available.
Yes
WebGPU/WGSL have a conformance test suite (
https://github.com/gpuweb/cts) that is regularly pulled into Chromium and part of the testing of Dawn/Tint in Chromium. While the CTS can be embedded in WPT, the WebGPU team opted to keep it separate in Chromium testing to use a customized harness for robustness and performance.
Flag name on about://flags
No information provided
Finch feature name
WebGPUEnabledEnabledToggles
Rollout plan
Will ship enabled for all users
Requires code in //chrome?
False
Tracking bug
https://crbug.com/528245806
Estimated milestones
No milestones specified
Anticipated spec changes
Open questions about a feature may be a source of future web compat or
interop issues. Please list open issues (e.g. links to known github
issues in the project for the feature specification) whose resolution
may introduce web compat/interop risk (e.g., changing to naming or
structure of the API in a non-backward-compatible way).
No information provided
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5080544005193728?gate=6068538249969664