3 ms·

I'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

I'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.