-
Notifications
You must be signed in to change notification settings - Fork 353
Add "core-features-and-limits" to spec #5147
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
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
Currently since Compat is in the spec yet, this is always available on adapters and always auto-enabled on devices.
Contributor
|
Previews, as seen when this build job started (e31b7a0): |
mwyrzykowski
approved these changes
Apr 9, 2025
Contributor
Author
|
@jimblandy for editor review (brandon is out) |
toji
approved these changes
Apr 16, 2025
Member
toji
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.
LGTM with one comment.
Contributor
GPU Web WG 2025-04-09 Atlantic-time
|
kainino0x
added a commit
to kainino0x/webgpu-headers
that referenced
this pull request
Jun 26, 2025
This was added in the upstream WebGPU API and should be reflected here. gpuweb/gpuweb#5147
kainino0x
added a commit
to webgpu-native/webgpu-headers
that referenced
this pull request
Jun 26, 2025
These were added in the upstream WebGPU API and should be reflected here. - gpuweb/gpuweb#5147 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.) - gpuweb/gpuweb#5160 - gpuweb/gpuweb#5226 The 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.
juj
added a commit
to juj/wasm_webgpu
that referenced
this pull request
Sep 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
api resolved
Resolved - waiting for a change to the API specification
api
WebGPU API
compat
WebGPU Compatibility Mode
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.
Add this to the main spec so that browsers can start implementing/shipping it. This allows applications to start relying on the presence of this feature name as soon as browsers ship it.
Currently since Compat is in the spec yet, this is always available on adapters and always auto-enabled on devices.
Fixes #5127