Contact emails
geoffl...@google.com

Explainer
None


Specification
https://github.com/gpuweb/gpuweb/commit/b39d86d356eb759d7564bc7c808ca62fce8bbf3e


Summary

Adds an optional field to WebGPU texture view creation to request a subset of 
the usage flags from the source texture. By default, texture view usage 
inherits from the source texture but there are view formats which can be 
incompatible with the full set of inherited usages. Adding a usage field to 
texture view creation allows the user request a subset of the source texture's 
usages that are valid with the view format and specific to their intended usage 
of the texture view. WebGPU implementations can also optimize the creation of 
low level resources and improve performance when using views with more 
specialized usage flags.



Blink component
Blink>WebGPU


TAG review
None


TAG review status
Not applicable


Risks




Interoperability and Compatibility

This feature has been approved in W3C GPU for the Web WG meetings including 
participants from Safari and Firefox: 
https://github.com/gpuweb/gpuweb/wiki/GPU-Web-2024-07-24#createtexture-does-not-validate-viewformats-against-usage-4426


Gecko: No signal

WebKit: Closed Without a Position 
(https://github.com/WebKit/standards-positions/issues/294#issuecomment-1877411933)

Web developers: No signals

Other signals:


WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it 
has potentially high risk for Android WebView-based applications?

None




Goals for experimentation




Ongoing technical constraints

None



Debuggability

None



Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, 
ChromeOS, Android, and Android WebView)?
No
All platforms will eventually have support. Will immediately be available on 
Android, Android WebView, ChromeOS, Mac, and Windows, where hardware support is 
available. Linux is planned to have WebGPU support in the future, so this 
feature will become available when WebGPU does.



Is this feature fully tested by web-platform-tests?
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. Tests were added in this PR: 
https://github.com/gpuweb/cts/commit/1746bcbc10a809cbadb3b131675b885ed08d9da5



Flag name on chrome://flags
None


Finch feature name
WebGPU.Enabled:UnsafeFeatures


Requires code in //chrome?
False


Tracking bug
https://bugs.chromium.org/363903526


Estimated milestones

No milestones specified



Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5155252832305152


This intent message was generated by Chrome Platform Status.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6703fdeb.2b0a0220.e48b7.040e.GAE%40google.com.

Reply via email to