4 ms·
Safari hasn’t joined the standards yet. You can do one code base for FF and Chrome, but Safari is a totally different beast.
by ernsheong 8y ago
Safari hasn’t joined the standards yet. You can do one code base for FF and Chrome, but Safari is a totally different beast.
- evermike 8y agoMoreover, Apple is deprecating legacy Safari Extensions now and pushing developers to transition to Safari App Extensions – which are offered through traditional Mac apps via the Mac App Store. More here - https://9to5mac.com/2018/06/09/safari-12-extensions-more/ https://9to5mac.com/2018/06/09/safari-12-extensions-more/ It's another headache for us. So far we did not find any good step-by-step article on how to do it.
- maio 8y agoWe have pretty complex extension so we decided to write Chrome API compatibility layer. It allows us to run our existing Chrome extension as an Safari app. extension. Check out https://github.com/avast/topee https://github.com/avast/topee - It's work in progress (but already complete enough for our use case).
- maio 8y agoCheck out https://github.com/avast/topee https://github.com/avast/topee - It allows us to use same codebase for Chrome and Safari (app. extension).