3 ms·
They did not just broaden the API. Previously, extensions were written in Javascript, roughly following open web standards[0]. This let you write your extension
by tristanho 7y ago
They did not just broaden the API. Previously, extensions were written in Javascript, roughly following open web standards[0]. This let you write your extension (nearly) once and have it work in all web browsers.
Now, all of those Javascript extensions are deprecated (users can no longer install them). If you want your extension to work, you now have to rewrite the majority of it from scratch in Swift[1]
[0] https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...
[1] https://developer.apple.com/documentation/safariservices/safari_app_extensions/converting_a_legacy_safari_extension_to_a_safari_app_extension https://developer.apple.com/documentation/safariservices/saf...
- kartickv 7y agoThanks for this information. How do the capabilities of the new API differ from the old one? If a developer is willing to put in the effort to do what Apple says, what extra capabilities do users get, and what existing capabilities are taken away? I'm not asking about ad- / content-blockers, because that issue has been discussed many times and there's no value in rehashing that discussion. I'm asking about OTHER TYPES of extensions.