We would be willing to pay it if Safari adopted the extensions standard. No it was not, whilst we are not a fan of the $100 charge due to our past experiences with Apple. The discussion lasted many weeks and it was not something we took lightly. Supporting this change would mean the codebase for RES would not be unified.ĭropping Safari support was never solely about money as many think it is, we do not have a vendetta against Apple. This would require significant investment from the development team to support the browser, as well as core developers having access to Xcode. Safari is not adopting this standard and instead moving to their own format, with a strong reliance on Xcode. This is hugely beneficial as you can develop for all major browsers from a single code base. This provides a single API across all browsers. Major browsers such as Google Chrome, Microsoft Edge and Mozilla Firefox were all adopting a standard commonly known as "WebExtensions". It ultimately came down to the direction development of Safari extensions was heading. We want to support Safari and provide a good user experience for all, however we need Apple's support with this by improving extension development and publishing experiences.Īpple have announced that as of Safari 12, support for this style of extension will be deprecated and will no longer work. OriginalĪs of RES v5.2.2, Safari is no longer a supported browser and will not receive updates or support from the development team. We welcome any other developer to work with us to support Safari. Apple have announced that Safari 14 will support WebExtensions, upon review and tests by the RES development team we are unable to support it at this time due to a large lack of API support that RES relies on, to get RES working on Safari at this time would require significant time and support investments that the development team does not have.
0 kommentar(er)
