- Notifications
You must be signed in to change notification settings - Fork2.4k
Chrome 143 WebGPU texture-component-swizzle feature#28411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Chrome 143 WebGPU texture-component-swizzle feature#28411
Uh oh!
There was an error while loading.Please reload this page.
Conversation
github-actionsbot commentedNov 7, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Tip: Review these changesgrouped by change (recommended for most PRs), orgrouped by feature (for large PRs). |
caugner commentedNov 12, 2025
Note that this will be partially fixed by#28226, so some of the statements will become "mirror" again, except the ones where Chrome has two notes. |
caugner left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
We need to runnpm ci && npm run fix once on this branch, which will revert some now Chrome Android statements to mirror.
As for other changes, I left some comments. (Sorry, reviewed last week and missed to submit.)
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com>
Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com>
Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com>
Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com>
Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com>
Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com>
chrisdavidmills commentedNov 22, 2025
Thanks! I ran the command as suggested and also added a missing comma. |
caugner left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Could we extract the other changes to a separate PR?
This should be straight-forward:
- Copy the branch (
git checkout -b webgpu-fixes) - Remove the
swizzlefeatures in that branch.
Then we can merge that PR first, afterwards mergemain into this one, which would only leave adding the new swizzle features.
| "chrome_android":"mirror", | ||
| "chrome_android": { | ||
| "version_added":"139", | ||
| "notes":"Available on all adapters and enabled automatically on all devices even if not requested." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I understand that this is note is pre-existing, but what does it mean for web developers? Are there certain things that don't work, and why does it not justifypartial_implementation: true?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
It is a feature that represents the basic, core featureset of WebGPU without requesting any extra features or advanced featuresets (which may well follow in the future). It is always available unless your GPU Adapter is set to "compatibility mode". I'm not 100% sure why they needed a specific feature name to represent the feature status quo.
chrisdavidmills commentedNov 25, 2025
Sure. Done in#28525. |
This pull request has merge conflicts that must be resolved before it can be merged. |
Summary
Chrome 143 adds support for the WebGPU
texture-component-swizzlefeature, which, when enabled, allows usage of thecreateView()method'sswizzleoption that allows developers to perform color swizzles.Seehttps://chromestatus.com/feature/5110223547269120.
This PR adds a data point for both the feature and the option.
I also took this opportunity to clean up the rest of the Chrome feature data, as a bunch of the entries weren't quite right (the Chrome Android data shouldn't mirror Chrome when Chrome is marked partial implementation and has a note, neither of which are relevant to CxA).
Test results and supporting details
Related issues