Skip to content
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

Chrome Android 121 supports Navigator.gpu + Canvas webgpu_context #25630

Merged
merged 2 commits into from
Jan 10, 2025

Conversation

caugner
Copy link
Contributor

@caugner caugner commented Jan 10, 2025

Summary

Chrome Android supports Navigator.gpu.

Test results and supporting details

All GPU features that were first supported in Chrome Desktop 113, appear to be supported in Chrome Android 121, so I have set the value accordingly.

Checked with Chrome Android 128 via BrowserStack Live.

Related issues

Fixes #22159, complementing #23493.

@caugner caugner requested a review from Elchi3 January 10, 2025 11:21
@github-actions github-actions bot added data:api Compat data for Web APIs. https://developer.mozilla.org/docs/Web/API size:xs [PR only] 0-6 LoC changed labels Jan 10, 2025
Copy link
Member

@Elchi3 Elchi3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you want to make the same change on the following features for consistency?

  • api.HTMLCanvasElement.getContext.webgpu_context
  • api.OffscreenCanvas.getContext.webgpu_context
  • api.WorkerNavigator.gpu

@tidoust
Copy link
Contributor

tidoust commented Jan 10, 2025

I don't know how/whether you capture that in other cases, but I believe support remains somewhat platform specific: "Android 12 and greater powered by Qualcomm and ARM GPUs" according to https://developer.chrome.com/blog/new-in-webgpu-121

Worth a note as done for Chrome on desktops?

@caugner
Copy link
Contributor Author

caugner commented Jan 10, 2025

Do you want to make the same change on the following features for consistency?

  • api.HTMLCanvasElement.getContext.webgpu_context
  • api.OffscreenCanvas.getContext.webgpu_context
  • api.WorkerNavigator.gpu

Fixed in 9a30024.

@github-actions github-actions bot added size:s [PR only] 7-24 LoC changed and removed size:xs [PR only] 0-6 LoC changed labels Jan 10, 2025
@caugner caugner changed the title Chrome Android supports Navigator.gpu Chrome Android supports Navigator.gpu + Canvas webgpu_context Jan 10, 2025
@caugner caugner changed the title Chrome Android supports Navigator.gpu + Canvas webgpu_context Chrome Android 121 supports Navigator.gpu + Canvas webgpu_context Jan 10, 2025
@caugner caugner requested a review from Elchi3 January 10, 2025 13:21
Copy link
Member

@Elchi3 Elchi3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Claas! 👍

@Elchi3
Copy link
Member

Elchi3 commented Jan 10, 2025

I don't know how/whether you capture that in other cases, but I believe support remains somewhat platform specific: "Android 12 and greater powered by Qualcomm and ARM GPUs" according to https://developer.chrome.com/blog/new-in-webgpu-121

Worth a note as done for Chrome on desktops?

Could be done as a follow up but I think it is hard for us to track support at this level of detail. (not sure if support would ever go further into the past, so maybe it would be at least a somewhat stable note?).

@Elchi3 Elchi3 merged commit d504098 into main Jan 10, 2025
11 checks passed
@Elchi3 Elchi3 deleted the fix-navigator-gpu-chrome-android branch January 10, 2025 13:31
@tidoust
Copy link
Contributor

tidoust commented Jan 10, 2025

Could be done as a follow up but I think it is hard for us to track support at this level of detail. (not sure if support would ever go further into the past, so maybe it would be at least a somewhat stable note?).

That certainly works for me. One reason I'm thinking that may be worth noting somewhere is that the underlying Chromium bug says: "We estimate this will cover about half of WebGPU-capable Android devices." In other words, unless things have changed, WebGPU probably only works on ~50% of Android devices today (possibly less depending on what "WebGPU-capable" means in practice), even if these devices run the latest version of Chrome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data:api Compat data for Web APIs. https://developer.mozilla.org/docs/Web/API size:s [PR only] 7-24 LoC changed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

WebGPU - Supported in Chrome Android since 121
3 participants