Chrome 140 accepts GPUTexture instead of GPUTextureView in two more places
#28245
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
github-actions
bot
added
data:api
Contributor
|
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
bentalakai21-ux
approved these changes
Oct 20, 2025
github-actions
bot
added
the
merge conflicts 🚧
Contributor
|
This pull request has merge conflicts that must be resolved before it can be merged. |
caugner
requested changes
Oct 24, 2025
Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com>
github-actions
bot
removed
the
merge conflicts 🚧
caugner
changed the title
GPUTexture instead of GPUTextureView in two more places
caugner
approved these changes
Oct 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Summary
In Chrome 140+, there are multiple places in WebGPU methods where a
GPUTextureViewwas expected, but now you can specify aGPUTextureas a shorthand, provided a defaultGPUTextureViewis desired (it is equivalent to aGPUTextureViewcreated using a call toGPUTexture.createView()with no descriptor specified).See https://developer.chrome.com/blog/new-in-webgpu-140#shorthand_for_using_texture_where_texture_view_is_used.
This PR adds data points in the appropriate places.
Test results and supporting details
Related issues