3 ms·
Yes, they've migrated to a new multiprocess architecture and the extra isolation requires new approach to integrating extensions. Previous extension API assumed
by pornel 9y ago
Yes, 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.