4 ms·
Feels like I'm missing some background here - what happened between 56 and 57 that made it necessary to port extensions? Some revolutionary architectural change
by alkonaut 9y ago
Feels like I'm missing some background here - what happened between 56 and 57 that made it necessary to port extensions? Some revolutionary architectural change?
- mattashii 9y agoFirefox stopped the support for legacy (non-WebExtension) APIs, and secondly FF57 introduced many new WebExtension APIs as 'replacements', making it only feasable to implement TST using WebExtension in FF57+. As mentioned, some APIs are missing to allow the last plugins to be rewritten as WebExtension versions, but it is close to feature-compatible with FF56- APIs.
- AlphaWeaver 9y agoI'm not sure if it was between 56 and 57, but Firefox recently switched to using web extensions, which is the same kind of extensions that Chrome uses, compared to Firefox extension types that it used previously. Therefore existing Firefox extensions had to be updated.
- mintplant 9y ago> which is the same kind of extensions that Chrome uses Sort of. The WebExtensions API aims to be a superset of Chrome's extension API. WebExtensions aren't and won't be limited to Chrome's feature set and Mozilla is in the process of rapidly expanding their capabilities. As opposed to the previous Firefox Add-ons API, which essentially exposed a ton of unstable internal surface area to dynamically-loaded third-party code, WebExtensions provide a stable, explicit interface that Mozilla can support without breaking things between releases or due to architectural changes like e10s/multi-process. The kinds of improvements Mozilla wants to make in Firefox going forward would end up breaking tons of extensions anyway, over and over again with each significant change. This way, there only needs to be one migration to the stable WebExtensions API.
- pornel 9y agoYes, they've migrated to a new multiprocess architecture and the extra isolation requires new approach to integrating extensions. Previous extension API assumed UI, pages and everything else lived in the same process.
- kasabali 9y agomultiprocess was a different event and it happened well before Firefox 56 breakage.
- pornel 9y agoIt wasn't enabled for users who had any old extensions installed.
- noisem4ker 9y ago"Legacy" addons could be made compatible with the newer multiprocess design. See: https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox$revision/993443 https://developer.mozilla.org/en-US/Add-ons/Working_with_mul... Many developers went through the effort only to see support for their addons scrapped altogether a couple months later. Fortunately, that was quick enough for Mozilla to sweep under the "legacy extensions are unfixable and unmaintainable" rug.
- syshum 9y agoin 2015/2016 Mozilla announced they were screw over all the developers and power users by removing all Low Level API's, XUL and XPCOM in place they were going to turn FF into a Chrome Clone and only support the Microsoft / Google WebExtentions API model which is very very limited in what it can do But goes well with them Caving to MS/Netflix/Google with EME as well