[minor breaking] Add new feature names from upstream JS API #551
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was added in the upstream WebGPU API and should be reflected here. gpuweb/gpuweb#5147
kainino0x
commented
Jun 26, 2025
Collaborator
Author
|
Actually I should add TextureFormatsTier1/2 while I'm at it. |
kainino0x
changed the title
kainino0x
changed the title
lokokung
approved these changes
Jun 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These were added in the upstream WebGPU API and should be reflected here.
Ordered at the top for consistency even though it changes the numbering of everything else.
Also fixed the ordering of TimestampQuery to match since the numbering is changing anyway. (Even though the ordering doesn't really matter because it's nonobservable upstream and there isn't really an ordering.)
texture-formats-tier1gpuweb/gpuweb#5160texture-formats-tier2gpuweb/gpuweb#5226The renumbering is technically a breaking change because it changes the ABI (which shouldn't matter right now) and could affect code that depends on comparing enum values or hard-coded integer versions of them.