-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Chrome 138 pass GPUBuffer directly as binding resource #28212
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
caugner
merged 5 commits into
mdn:main
from
chrisdavidmills:pass-gpubuffer-directly-as-binding-resource
Oct 22, 2025
Merged
Chrome 138 pass GPUBuffer directly as binding resource #28212
caugner
merged 5 commits into
mdn:main
from
chrisdavidmills:pass-gpubuffer-directly-as-binding-resource
Oct 22, 2025
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
Contributor
|
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
caugner
requested changes
Oct 17, 2025
Co-authored-by: Claas Augner <[email protected]>
Co-authored-by: Claas Augner <[email protected]>
caugner
requested changes
Oct 17, 2025
Contributor
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.
Sorry, missed the descriptions.
Let's reflect the feature ID in it.
Co-authored-by: Claas Augner <[email protected]>
Co-authored-by: Claas Augner <[email protected]>
caugner
approved these changes
Oct 22, 2025
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Chrome 138 adds the ability for a
GPUBufferto be passed directly into aGPUDevice.createBindGroup()call as a binding resource in place of aGPUBufferBindingobject, provided the defaultsizeandoffsetvalues are being used.See https://developer.chrome.com/blog/new-in-webgpu-138#shorthand_for_using_buffer_as_a_binding_resource.
This PR adds a data point for the new feature.
Test results and supporting details
Related issues