-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Safari Support #995
Comments
Tracked it down to an algorithm named
|
Thanks for reporting this @lightninglu10. It is a known issue for a while as we focused on developing for Chrome and Firefox (due to their WebRTC support). See compat table here: libp2p/js-libp2p-crypto#18 This means that missing alg need to be shimmed. Is this something you would like to help with? |
A major version of Safari (11.0) was released a couple of weeks ago. The WebCrypto API section of the release notes is a little vague and the JS API docs are even less informative, but the release appears to include recent commits to WebKit adding support for the remaining WebCrypto spec ciphers mentioned in libp2p/js-libp2p-crypto#18. See: https://bugs.webkit.org/show_bug.cgi?id=166746 |
Do we have a volunteer to go and test these new grounds? Thank you for the update, @bertrandrustle |
Here's an exhaustive browser test of the WebCrypto API: Source code: When Safari is detected the test shims in Safari's soon-to-be-removed So that interface already seems to support everything IPFS needs. After modifying the test to make Safari use the standard |
Got However, there is a merged PR with a working commit though, vibornoff/webcrypto-shim@ae3e9fa made a PR to our fork that fixes it and now it works 🎉 |
PR linked in previous commit has been merged and |
Ohh coool thanks @diasdavid !! |
Type: Bug
Severity: High
Description: IPFS does not work in Safari. It looks like something dealing with the webcrypto package here: libp2p/js-libp2p-crypto#18
Getting an error in Safari that
alg — ipfs.min.js:42864SyntaxError: Bad algorithm name
Is there anyway to remedy this?
The text was updated successfully, but these errors were encountered: