Safari build #387
trvrplk
started this conversation in
Tech Office
Replies: 1 comment 11 replies
-
I plan to release to Safari eventually, but as I understand it, Apple would have to review every version I want to publish, and that's a bag of worms I'm not ready to open with how rapidly development is going. It'll be on the table officially when we hit v1.0.0, i.e. every planned feature is built. |
Beta Was this translation helpful? Give feedback.
11 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Safari recently (last year I believe) switched to the WebExtensions API, and because of this XKit Rewritten runs pretty much flawlessly in it. Following this official documentation I was very easily able to convert the Firefox version to a Safari extension—you just need to have a Mac with Xcode, run a certain command to convert the extension to an Xcode project, then compile it. I've had no issues, but there's one problem: because I don't have a developer account, the extension's unsigned, which means I need to re-enable unsigned extensions every time I relaunch Safari. If anyone has a developer account, it'd be really easy and I'm sure helpful to a lot of people to put out an unofficial (or official!) Safari build.
(If anyone wants to run the unsigned version I compiled, here's a zip with the binary. Just make sure to enable unsigned extensions or it won't work.)
Beta Was this translation helpful? Give feedback.
All reactions