Open MaartenLMEM opened 3 years ago
So far what we know :
The advantages of having the extension on Safari :
The remaining questions:
Apparently Apple made the process super easy, so as to maximize the amount of developpers porting extensions to safari.
xcrun safari-web-extension-converter .
^This should do the tick when xcode is installed from a macbook with a xpi unzipped.
i can't test since I don't own an apple device.
I managed to install the extension on Chrome, by converting a chrome version of the application.
Matching context and xpath seem to work.
Subscribing to channels didn't work (saying app in not installed), and the logo doesn't turn grey when a notice already appeared.
The testing on my hand, was very tedious, since I didn't own a mac I used https://github.com/kholia/OSX-KVM to create a virtual machine and it was slow and several crashes occurred (Big Sur being not fully compatible).
@JalilArfaoui
@zhinu From my point of view, job is done here. And with good news.
Now, what about creating a new card in the backlog : Create a package to publish Dismoi on Safari ? And adding in this card some checklist with requirements and specific changes needed ?
The authorization requested and explained by Safari
Etre présent sur Safari nous permettrait de gagner beaucoup d'utilisateurs sur ordinateurs. Safari avait son propre écosystème mais semble avoir évoluer vers une meilleure compatibilité.
Mais quelle est la complxité désormais exactement ? Peut on la publier en août par exemple ?
https://www.appsystem.fr/197990/safari-14-apple-indique-comment-ajouter-extensions-chrome-firefox-sur-son-navigateur/