Hi Alex, I've added https://github.com/gpuweb/gpuweb/issues/5154 as an explainer. This was a user-requested feature for the WebGPU WG. It went through prioritization and discussion there. It adds QoL polyfills over existing builtins. Everyone (including myself) who has tried to write those formulae themselves has failed at least once so there was good value for implementations to provide the builtin (and overflow safety checks).
Thanks, Alan On Mon, Mar 23, 2026 at 2:52 PM Alex Russell <[email protected]> wrote: > Hey Alan, > > Thanks for sending this Intent. I'm glad to see a team go straight to > shipping when we have confidence that a feature is worthwhile! > > That said, it's a bit surprising that we don't have any developer signals. > Likewise, I can't find an Explainer or any example code from the links in > the Intent that will benefitfeature. What does this improve? Who will use > it? How will it make things better for users and/or developers? > > Best, > > Alex > > On Monday, March 23, 2026 at 7:04:03 AM UTC-7 Chromestatus wrote: > >> *Contact emails* >> [email protected] >> >> *Explainer* >> *No information provided* >> >> *Specification* >> https://github.com/gpuweb/gpuweb/pull/5554 >> >> *Summary* >> Functionality added to the WebGPU spec after its first shipment in a >> browser. Adds two new compute shader built-in values for user quality of >> life. These are implemented for all backends (as polyfills of existing >> built-in values). >> >> *Blink component* >> Blink>WebGPU >> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EWebGPU%22> >> >> *Web Feature ID* >> webgpu <https://webstatus.dev/features/webgpu> >> >> *Motivation* >> This feature adds two new compute built-in values to WGSL. They are >> quality-of-life additions whose implementations are polyfilled on top of >> existing values. >> >> *Initial public proposal* >> *No information provided* >> >> *TAG review* >> *No information provided* >> >> *TAG review status* >> Pending >> >> *Goals for experimentation* >> None >> >> *Risks* >> >> >> *Interoperability and Compatibility* >> *No information provided* >> >> *Gecko*: No signal ( >> https://github.com/mozilla/standards-positions/issues/1205#issuecomment-3312534193 >> ) >> >> *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? >> *No information provided* >> >> >> *Debuggability* >> *No information provided* >> >> *Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, ChromeOS, Android, and Android WebView)?* >> Yes >> >> *Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* >> Yes >> WebGPU conformance tests added in https://github.com/gpuweb/cts/pull/4595 >> >> *Flag name on about://flags* >> Enable Unsafe WebGPU >> >> *Finch feature name* >> UnsafeWGSLFeatures >> >> *Rollout plan* >> Will ship enabled for all users >> >> *Requires code in //chrome?* >> False >> >> *Tracking bug* >> https://crbug.com/tint/482840564 >> >> *Estimated milestones* >> Shipping on desktop 148 >> Shipping on Android 148 >> Shipping on WebView 148 >> >> *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/5071243424432128?gate=6507584288849920 >> >> 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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABg%2BrB41HHKCY697rceUjpheBEQzXvmfEGStAAPT_2HZmx5CDg%40mail.gmail.com.
