4 ms·

The main problem with legacy extensions is that they won't work with multiprocess firefox by design. Multiprocess is the only way forward, because of the enormo

The main problem with legacy extensions is that they won't work with multiprocess firefox by design. Multiprocess is the only way forward, because of the enormous speed and stability benefits. Unfortunately Mozilla has rushed the transition, and there hasn't been enough time to add important APIs and for developers to update their extensions. Firefox 57 is on the verge of being released, and there are still many addons which aren't webextension compatible.

kirillkh 9y ago
Isn't v55 already multiprocess? How are these extensions working right now?
- johnny22 9y ago
  many of the apis were shimmed in such a way so that they'd work, but could still slow down the browser. Those shims will disappear.
- zanny 9y ago
  If you have any legacy extensions installed multiprocess is disabled. If you don't have any, it is turned on.
  - scott_karana 9y ago
    Not correct. Some legacy plugins work fine: the add-ins store relied on user testing and flagging to confirm which still worked. https://developer.mozilla.org/en-US/Add-ons/SDK/Guides/Multiprocess_Firefox_and_the_SDK https://developer.mozilla.org/en-US/Add-ons/SDK/Guides/Multi...