Skip to content

Conversation

@greggman
Copy link
Collaborator

Firefox and Chrome have supported this for 3-4 months or more. Safari started supporting it in 2025-12 as of Tahoe 26.2. We're planning to switch the samples to use this new more convenient method but want to be able to tell users on older browsers to update their browsers.

@greggman
Copy link
Collaborator Author

greggman commented Jan 22, 2026

I snuck this into quitIfWebGPUNotAvailable. I get that's a little fishy.

I could

  1. leave it as is
  2. rename it to quitIfWebGPUNotAvailableOrMissingFeatures
  3. add a 2nd call quitIfWebGPUMissingFeatures and make every sample call it.
  4. not put it here and only put it in src/main.ts
  5. ?

I worry that checking in each sample will lead other devs to check. I think we'd prefer they don't check and just use this new way and tell users to upgrade. Otherwise, these checks will likely propagate for years.

Firefox and Chrome have supported this for 3-4 months or more.
Safari started supporting it in 2025-12 as of Tahoe 26.2.
We're planning to switch the samples to use this new more
convenient method but want to be able to tell users on older
browsers to update their browsers.
@greggman greggman force-pushed the add-warning-for-missing-features branch from 1d1e657 to a20bac4 Compare January 22, 2026 00:07
Copy link
Collaborator

@kainino0x kainino0x left a comment

Choose a reason for hiding this comment

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

lgtm, I prefer option 2 (just rename)

@greggman
Copy link
Collaborator Author

renamed

@greggman greggman merged commit 626a4b8 into webgpu:main Jan 22, 2026
1 check passed
@greggman greggman deleted the add-warning-for-missing-features branch January 22, 2026 21:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants