Port to Safari #7
Comments
|
With new extension it should be done for Safari as well. In new Big Sur and Safari extensions become somewhat big thing. Not sure if apple make it easier to convert Chrome extensions. |
|
It is a bit easier now, and I do have it mostly working at the moment, but I need to take some time to properly test it. There's also the matter of cost. To release a Safari extension, I need to pay for an Apple developer license. For this reason, I'm considering charging for this extension. Just the minimum, and it feels weird to be charging for something that is free on every other platform, but such is the price of dealing with Apple. Do you have any thoughts on this? Would you be willing to pay for the Safari extension? |
|
Of course! But calculate price that it will be reasoanble for you to cover all cost and have something for coffee.... Your extension is gem. It is true, the apple sheeps will pay :) |
|
I would love to have this on Safari and would pay for it. I understand the cost of doing business with Apple and that you have to recoup the cost. My workflow currently entails opening a link in chrome and using the extension from there, which is a pain to deal with. P.S. thank you for all the Obsidian plugins! |
|
This would be great :) |
|
I'd love to see this ported to safari, and will pay for it, the price to deal with apple... |
|
Oh yeah, this would be nice for any markdown workflow. |
|
@deathau thanks for building this! It seems that "Download images" is not supported - is this a problem with Safari? |
|
Hey! Just grabbed this app from the apps store - happy to pay you a few $$. However it's not installing as an app. I just get the following popup, but the button doesn't work. And the extension isn't showing up in prefernces>extensions. |
|
@jaredosborne I noticed in my testing, too, that the button didn't seem to do anything, but it did show up in the Safari extensions. Not sure what's up with this. What version of MacOS / Safari are you on? |
|
Safari 14.0.2 Haven't rebooted system, but just shut and reopened safari and same. Extension not showing. |
|
Same problem - does not seem to install. The little installation window opens but the button labelled "Quit and Open Safari Extensions Preferences..." (what does this text actually mean?? - quit what?) does not appear to do anything (and the extension does not appear in the Extensions list in Safari, nor is it added to the displayed Safari extensions). Tried quitting Safari, rebooting system (Big Sur 11.4) |
|
I'm really not sure why it's not appearing in the extensions list The way Apple have us developing Safari extensions is somewhat confusing: They exist as part of a desktop mac app. In this case the mac app is just the default template provided by Apple: A window with the icon and a button to quit the app and open safari extension preferences so you can enable the extension. So to answer your question, that's what the button does: quits the desktop mac app whose only available action is to quit. It's just a delivery mechanism for the extension. As for why the extension is not showing up in safari itself, that's the actual issue here, and I'm kinda clueless, to be honest. If I had to guess, it would be some security related thing on Big Sur (and up) and my poor aging mac mini refuses to upgrade. I'll do some more digging, but at the moment I don't have a solution. |
|
Many thanks for the speedy reply and explanation of the mysterious wording in the button!
I look forward to a fix in due course - meanwhile the FireFox version seems fine but I find it tiresome to swap out of Safari all the time.
Cheers
Jim (in Wellington, not so far from Melbourne really and free, so far, of the virus)
… On 22/06/2021, at 2:58 PM, deathau ***@***.***> wrote:
I'm really not sure why it's not appearing in the extensions list
The way Apple have us developing Safari extensions is somewhat confusing: They exist as part of a desktop mac app. In this case the mac app is just the default template provided by Apple: A window with the icon and a button to quit the app and open safari extension preferences so you can enable the extension. So to answer your question, that's what the button does: quits the desktop mac app whose only available action is to quit. It's just a delivery mechanism for the extension.
As for why the extension is not showing up in safari itself, that's the actual issue here, and I'm kinda clueless, to be honest. If I had to guess, it would be some security related thing on Big Sur (and up) and my poor aging mac mini refuses to upgrade.
I'll do some more digging, but at the moment I don't have a solution.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARDOYMZ6M7OQUWL66L64D33TT7335ANCNFSM4NBG6LIQ>.
|
|
I'm having this issue on Mojave with Safari 12, so it's not a Big Sur thing. |
|
Damn. I'm stuck on Catalina (is Mojave before or after? I hate this naming scheme). I genuinely wonder how I can get more information about this issue... As for refunds, I'm not familiar with the process, but from what I can tell on a quick Google search you actually have to go through apple itself? https://blog.supereasyapps.com/mac-app-store-refund-in-6-steps-how-to-get-a-refund-for-any-macos-app I tried looking in my developer portal and could not see anything to do with issuing refunds. It just doesn't seem like a thing it's possible for me to do from my end. Even as a dev, you give up a lot of control to Apple when using their ecosystem. |
|
Mojave is 10.14 |
|
Agreed. I would much rather have the extension fixed than a refund (which I have not even attempted), hoping a fix will appear soon!
… On 9/07/2021, at 6:48 PM, Odroid-Dude ***@***.***> wrote:
Mojave is 10.14
I'd rather the working extension than a refund
|
|
I poked around for a way to manually install the extension but didn't find anything in obvious locations |
|
@jeam-github and @Odroid-Dude I'm going to close this issue (as, to my mind, the port to Safari is "complete") and replace it with #76 (for Big Sur) and #111 (for Mojave). Please go subscribe to those issues and let me know if you figure anything out. |
No idea if there's even demand for this, as I haven't heard anything.
At first blush, it seems a bit more work to convert for Safari than between chromium/firefox
There is some guidance from Apple here: https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/SafariExtensionsConversionGuide/Chapters/Chrome.html
The text was updated successfully, but these errors were encountered: