Intent to Ship: WebGPU: `linear_indexing` feature

[Chromestatus]

Contact emails

alan...@google.com

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

Web Feature ID

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?

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.