Chrome 146 WebGPU compatibility mode featureLevel option#29551
Open
chrisdavidmills wants to merge 2 commits intomdn:mainfrom
Open
Chrome 146 WebGPU compatibility mode featureLevel option#29551chrisdavidmills wants to merge 2 commits intomdn:mainfrom
chrisdavidmills wants to merge 2 commits intomdn:mainfrom
Conversation
github-actions
Bot
added
the
data:api
Contributor
|
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
Contributor
Author
|
It would be good to get @beaufortfrancois to look at this data and comment on whether it makes sense. |
| "chrome": { | ||
| "version_added": "146", | ||
| "partial_implementation": true, | ||
| "notes": "Compatibility mode supported only on Android 5.0 and above (running OpenGL ES 3.1 and above)." |
Contributor
There was a problem hiding this comment.
@Kangz Is it safe to assume Android 5.0 for OpenGL ES 3.1 and above?
There was a problem hiding this comment.
10+ on everything but Imagineation where it is 13+. See https://source.chromium.org/chromium/chromium/src/+/main:gpu/config/webgpu_blocklist_impl.cc;drc=cad20a67c6aebeb31678884298a24fa9d061b0ee;l=118
Contributor
Author
There was a problem hiding this comment.
I've updated the Android version to 10.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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
Chrome 146 adds support for WebGPU compatibility mode: see https://chromestatus.com/feature/6436406437871616, and also see https://developer.chrome.com/blog/new-in-webgpu-146#support_webgpu_compatibility_mode_on_opengl_es_31 for more info and context.
This PR adds a data point for the
featureLeveloption of theGPU.requestAdapter()method, which is used to opt in to compatibility mode. Note that:featureLevelis recognized and can be used on any Chrome 146+ browser; however, at the moment, only old Android devices running OpenGL ES 3.1 and above will support compatibility mode. Support will be added later for other older device/API combinations. Hence, the partial implementation and the note, which still describes support on Chrome desktop as well as Android.featureLevel: "compatibility"set. Instead, you have to useadapter.features.has("core-features-and-limits")to test. If it returnsfalse, your adapter is in compatibility mode.Test results and supporting details
Related issues