Skip to content
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 #29

Closed
tjmehta opened this issue Feb 16, 2015 · 14 comments · Fixed by #1181
Closed

Safari support #29

tjmehta opened this issue Feb 16, 2015 · 14 comments · Fixed by #1181

Comments

@tjmehta
Copy link

tjmehta commented Feb 16, 2015

I love this plugin. I would love to see safari support. Thanks!

@tjmehta
Copy link
Author

tjmehta commented Feb 16, 2015

Octotree, another browser plugin I love has recently started supporting multiple browsers. It looks like a good example of how to support multiple browser plugin formats ( Firefox too #24). Check out the source here: https://github.com/buunguyen/octotree

@stefanbuck
Copy link
Member

The problem is not to build these extensions, but keep them up to date with the registries. Accutlay once per week I run a script which generates the cache list for the npm, bower and comperser registry.

I'm planning to move the core from a cache list to a live resolver solution, but I need time to develop it. Soon as this is done I can start thinking about a safari and firefox version 😉

@tjmehta
Copy link
Author

tjmehta commented Feb 21, 2015

Ah, I was wondering how you were doing the linking. Is it not possible to do everything clientside (maybe parse npmjs or bower websites for the github links - or maybe reverse engineer their apis)?

@stefanbuck
Copy link
Member

Yeah, that's the plan. I will start working on it soon 😉

@JaKXz
Copy link

JaKXz commented Jun 24, 2016

Any updates on the safari extension? The developer preview for Safari 10 is actually pretty good, IMO 😄

@stefanbuck
Copy link
Member

Nope, unfortanly not. Do you know if Safari 10 supports the WebExtension API?

@josephfrazier
Copy link
Member

I looked into this for a little bit, and found that while Safari doesn't support the WebExtension API, it might not be very difficult to shim it out, using something like https://github.com/kritollm/chrome-extension-api-for-safari-and-firefox

Another potential option could be to build a userscript version of the extension, so Safari users could install it using Tampermonkey, etc

@nikitavoloboev
Copy link

I too would love for Safari to be supported

josephfrazier added a commit to josephfrazier/browser-extension that referenced this issue Jan 15, 2018
This makes it easier to use on its own, as suggested in
OctoLinker#280 (comment)
@sindresorhus
Copy link

Safari will soon support the WebExtensions API:

@stefanbuck
Copy link
Member

Thanks for the update. Do you know if a developer account is required to submit web extensions? The developer program is super pricey to distribute a single free item.

@nesl247
Copy link

nesl247 commented Jul 10, 2020

Yes, it is still required. Though if you already have one for any purpose, you could use that.

I'd be willing to chip in to help pay for it.

@fregante
Copy link
Collaborator

Follow refined-github/refined-github#14 and refined-github/refined-github#3677 for more details.

Supporting Safari is not particularly difficult, but we still need help with auto-deployment to the App Store.

@fregante
Copy link
Collaborator

I can publish OctoLinker under my (SindreSorhus-sponsored) account if you want. I'm already publishing npmhub.

We still don't have auto publishing set up but even having an occasionally-updated version on the App Store would be pretty helpful for most.

@stefanbuck
Copy link
Member

Sure, I'm in. Thanks for making this possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

8 participants