Safari is the new IE.
The implementation doesn't use chrome specific API AFAIK, and it works on firefox.
> are very specifically Chrome-only. And it undoubtedly relies on a bunch of Chrome-only non-standards, too.
It does support all majors browers, except safari.
The reason why it doesn't work on Safari is even listed:
> Safari recently shipped support for SharedArrayBuffer and cross-origin isolation in a somewhat buggy state. In addition to this, it is still lacking a few other features which prevents us from shipping a working environment such as:
> Atomics.waitAsync > Lookbehind in regular expressions
> Note that none of above can be pollyfilled.
These are not "Chrome-only non-standards" and are parts of the officials JS/HTTP specs
The reason for my comment is that far too often these complaints are about some things that Chrome ships at neck-breaking speed.
If you go to MDN and click on multiple experimental APIs you'll find they do have a spec. And they are shipped in Chrome. And then you start reading the spec and it says "It is not a W3C Standard nor is it on the W3C Standards Track.": https://developer.mozilla.org/en-US/docs/Web/API