Firefox 145 supports WebGPU on macOS 26

[caugner]

Summary

Updates the notes for Firefox' partial implementation of WebGPU features to account for newly added macOS support.

Test results and supporting details

Source from issue: https://github.com/gpuweb/gpuweb/wiki/Implementation-Status#firefox

Related issues

Fixes #28555.

[github-actions]

Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

[caugner]

/cc @ErichDonGubler Can you confirm that macOS 26+ is supported from Firefox 145? Are there any noteworthy limitations compared to Windows support?

[caugner]

I'm still on macOS 15.7.2 Sequoia, and the BCD Collector Tests for api.GPU pass in Firefox 145 anyhow. This suggests we can omit the macOS version number in the notes.

Edit: WebGPU appears to be available in macOS 12.5 Monterey and higher:

[ErichDonGubler]

/cc @ErichDonGubler Can you confirm that macOS 26+ is supported from Firefox 145? Are there any noteworthy limitations compared to Windows support?

For where this is enabled, there should be no significant differences (modulo minor platform-specific bugs).

AFAIK this should be enabled on macOS Sequoia on Apple Silicon from 145 onwards, and other Apple Silicon devices should have access from 147 onwards. Intel Macs are still being tracked here: bug 2004105

CC @jimblandy and @andyleiserson to check my work here.

[caugner]

Firefox 145 and Firefox 146 only support macOS Tahoe, but the interfaces (like GPU) are available in all macOS versions, and the navigator.gpu property is also available; only navigator.gpu.requestAdapter() throws a DOMException: WebGPU is disabled by blocklist.

[caugner]

AFAIK this should be enabled on macOS Sequoia on Apple Silicon from 145 onwards, and other Apple Silicon devices should have access from 147 onwards. Intel Macs are still being tracked here: bug 2004105

CC @jimblandy and @andyleiserson to check my work here.

My confusion stemmed from the fact that the BCD collector tests for the WebGPU interfaces (and e.g. the navigator.gpu property) passed, because the interfaces/property are available. The DOMException happens only when the GPU is actually used.

For BCD, I will revert bcc0131, and mention that interfaces/property are available.

[ErichDonGubler]

Oh, derp, I meant Tahoe, and not Sequoia, in my earlier comment—the latest major version of macOS. Sorry for the confusion! 😅