5 ms·
WebExtensions were specifically announced alongside Electrolysis. This is not Mozilla's fault.
by Sylos 9y ago
WebExtensions were specifically announced alongside Electrolysis. This is not Mozilla's fault.
- jhasse 9y agoI guess extension developers didnt expect being forced to WebExtemsions only so soon.
- pseudalopex 9y agoWhen WebExtensions was announced, Electrolysis was already on by default in Developer Edition, and Mozilla planned to begin blacklisting incompatible extensions within 3 months.[1] The author of Tab Groups had just finished rewriting his extensions for Electrolysis.[2] He only gave up 18 months later, partly because of how frustrating Mozilla made the process of getting missing functionality added to WebExtensions. [1] https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/ https://blog.mozilla.org/addons/2015/08/21/the-future-of-dev... [2] https://web.archive.org/web/20170128013037/http://fasezero.com/lastnotice.html https://web.archive.org/web/20170128013037/http://fasezero.c...
- Sylos 9y agoYour link 1 is from 2015/08/21. Electrolysis was rolled out with Firefox 48 on 2016/08/02. The respective Developer Edition build was released on 2016/04/25.
- pseudalopex 9y agoElectrolysis development started in 2009. It was enabled by default in Developer Edition starting with Firefox 42 (2015/08/11) and opt-in before that. Nobody knew in August 2015 that Mozilla would delay the Electrolysis rollout, allow incompatible extensions would continue working into 2017, pick an arbitrary date to drop XUL extensions instead of tying it to WebExtensions milestones, drop the Add-on SDK at the same time, and not really support gradual porting.