Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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

Open
chrisdavidmills wants to merge13 commits intomdn:main
base:main
Choose a base branch
Loading
fromchrisdavidmills:webgpu-texture-component-swizzle-feature

Conversation

@chrisdavidmills
Copy link
Contributor

Summary

Chrome 143 adds support for the WebGPUtexture-component-swizzle feature, which, when enabled, allows usage of thecreateView() method'sswizzle option 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

@github-actionsgithub-actionsbot added data:apiCompat data for Web APIs. https://developer.mozilla.org/docs/Web/API size:l[PR only] 101-1000 LoC changed labelsNov 7, 2025
@github-actions
Copy link
Contributor

github-actionsbot commentedNov 7, 2025
edited
Loading

Tip: Review these changesgrouped by change (recommended for most PRs), orgrouped by feature (for large PRs).

@caugner
Copy link
Contributor

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

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.

chrisdavidmills reacted with thumbs up emoji

Copy link
Contributor

@caugnercaugner left a 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.)

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
Copy link
ContributorAuthor

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

Thanks! I ran the command as suggested and also added a missing comma.

Copy link
Contributor

@caugnercaugner left a 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:

  1. Copy the branch (git checkout -b webgpu-fixes)
  2. Remove theswizzle features 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."
Copy link
Contributor

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?

Copy link
ContributorAuthor

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
Copy link
ContributorAuthor

Could we extract the other changes to a separate PR?

This should be straight-forward:

1. Copy the branch (`git checkout -b webgpu-fixes`)2. Remove the `swizzle` features in that branch.

Then we can merge that PR first, afterwards mergemain into this one, which would only leave adding the new swizzle features.

Sure. Done in#28525.

@github-actions
Copy link
Contributor

This pull request has merge conflicts that must be resolved before it can be merged.

@github-actionsgithub-actionsbot added the merge conflicts 🚧This PR needs to merge latest "main" branch to resolve a merge conflict or other issue. labelNov 25, 2025
@github-actionsgithub-actionsbot added size:m[PR only] 25-100 LoC changed and removed merge conflicts 🚧This PR needs to merge latest "main" branch to resolve a merge conflict or other issue. size:l[PR only] 101-1000 LoC changed labelsNov 26, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@caugnercaugnerAwaiting requested review from caugner

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

data:apiCompat data for Web APIs. https://developer.mozilla.org/docs/Web/APIsize:m[PR only] 25-100 LoC changed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@chrisdavidmills@caugner

[8]ページ先頭

©2009-2025 Movatter.jp