-
Notifications
You must be signed in to change notification settings - Fork 25
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
Safari Support? #151
Comments
Error indicates that content script returns something other than a blob in content-script.js:17, or the FileReader API works a bit different way. Thats most likely due some differences in Safari. Extension is written in cross-compatible way and works in Chrome, so it should work in Safari and Explorer as well. Atleast for a while, as it almost completely breaks after manifest v3 lands. |
Hmm. Any suggestions of something I can try to fix this? |
There was also this when I first ran the converter, in case helpful:
|
Hi, just following up in case you had any ideas/suggestions of things to try. Thanks! |
You need to remove or try to find alternative methods to implement features that are relying those unsupported apis. |
I'm trying to port this to Safari, using the Safari Extension Converter. Don't really know what I'm doing, but converted with no further edits to the code. It successfully built and installed as an extension in Safari. Settings page works, added server info, gave permission to work on every website, and pressing the button in Safari successfully loads the transmission web interface. However, when I right click on a magnet or torrent link > Torrent Control > Add torrent (or Add torrent (Advanced)), nothing happens.
When I load the web inspector for the extension, this is the js error I see after trying to add a torrent:
Any suggestions? If I figure this out, I can fork and post releases for anyone wanting this capability on Safari (Mac & iOS). This repo seemed like a simple and reliable extension with updates and various client support. There are no torrent extensions for Safari that I could find.
The text was updated successfully, but these errors were encountered: