Could you please request privacy, security, enterprise, and debuggability bits in your chromestatus entry?

On 5/27/25 2:03 PM, Chromestatus wrote:


        Contact emails

g...@google.com


        Explainer

None


        Specification

https://gpuweb.github.io/gpuweb/#core-features-and-limits


        Summary

The 'core-features-and-limits' feature signifies a WebGPU adapter and device support the core features and limits of the spec. Explainer: https://gist.github.com/greggman/0dea9995e33393c546a4c2bd2a12e50e



        Blink component

Blink>WebGPU <https://issues.chromium.org/issues?q=customfield1222907:%22Blink>WebGPU%22>


        TAG review

None


        TAG review status

Not applicable


        Risks



        Interoperability and Compatibility

This feature has not yet been implemented in any browser. It has been approved by the GPU for the Web Community Group, with representatives from Chrome, Firefox, and Safari. See https://github.com/gpuweb/gpuweb/pull/5147 with approval from representatives of Firefox, Chrome, and Safari as well as links to minutes.



/Gecko/: Positive (https://github.com/gpuweb/gpuweb/pull/5147) This is already implemented in Firefox but WebGPU itself is still behind a flag.

/WebKit/: In development (https://github.com/gpuweb/gpuweb/pull/5147) This is already implemented in Safari but WebGPU itself is still behind a flag.

/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



        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, since those platforms already support WebGPU. 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
        
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?

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. All the tests about this feature in WebGPU CTS can be found through the below link: https://github.com/gpuweb/cts/pull/4228



        Flag name on about://flags

chrome://flags/#enable-unsafe-webgpu


        Finch feature name

WebGPU.Enabled:UnsafeFeatures


        Rollout plan

Will ship enabled for all users


        Requires code in //chrome?

False


        Tracking bug

https://issues.chromium.org/issues/418025721


        Availability expectation

Feature is available on Web Platform Baseline within 4 months of launch in Chrome. Safari, Firefox, and Chrome have all implemented this feature. Safari and Firefox have not yet shipped WebGPU to their stable versions but appear close to shipping. Chrome's support is currently behind a flag.


        Adoption expectation

Feature is already considered best practice. Chrome needs to ship so that developers can start following best practices. Currently they require hacky and non-perfect workarounds.


        Adoption plan

Major WebGPU libraries like three.js will adopt this feature soon after it's available in Chrome.


        Non-OSS dependencies

Does the feature depend on any code or APIs outside the Chromium open source repository and its open-source dependencies to function?

None


        Estimated milestones

Shipping on desktop     139
DevTrial on desktop     136
Shipping on Android     139
DevTrial on Android     136



        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).

N/A


        Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/4744775089258496?gate=6474886784221184

This intent message was generated by Chrome Platform Status <https://chromestatus.com>.
--
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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6835fe85.170a0220.2aa17e.17ba.GAE%40google.com <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6835fe85.170a0220.2aa17e.17ba.GAE%40google.com?utm_medium=email&utm_source=footer>.

--
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 visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/a288c524-2874-4100-862f-e83a23c36042%40chromium.org.

Reply via email to