3 ms·
Developers can't port to APIs that don't exist. Mozilla holding to the November deadline as implementation has slipped hasn't helped them in any way. Mozilla k
by pseudalopex 9y ago
Developers can't port to APIs that don't exist. Mozilla holding to the November deadline as implementation has slipped hasn't helped them in any way.
Mozilla kept pushing developers to make their XUL extensions multiprocess-compatible even after WebExtensions was announced. At one point, they were going to keep the multiprocess compatibility shims until the WebExtensions deadline, but then they decided to start removing them sooner.[1] SDK extensions were mostly multiprocess-compatible already.
Developers are currently maintaining multiple branches of their extensions because 52 ESR is missing APIs and 57+ won't support hybrid extensions. Aligning the WebExtensions transition with the ESR cycle would have made things a lot easier for them.
[1] https://blog.mozilla.org/addons/2017/02/16/the-road-to-firefox-57-compatibility-milestones/ https://blog.mozilla.org/addons/2017/02/16/the-road-to-firef...