By the end of 2017, and with the release of Firefox 57, we’ll move to WebExtensions exclusively, and will stop loading any other extension types on desktop. To help ensure any new extensions work beyond the end of 2017, AMO will stop accepting any new extensions for signing that are not WebExtensions in Firefox 53. Throughout the year we’ll expand the set of APIs available, add capabilities to Firefox that don’t yet exist in other browsers, and put more WebExtensions in front of users.
https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/
IOW, Firefox extension users have work to do in 2017. We must review the extensions we use or plan to use. To determine 1) whether they can/will be implemented as a WebExtension, and 2) whether there are any specific features that can't/won't be implemented due to WebExtension API shortcomings. We have to help extension developers get the WebExtension APIs they need. Without which some extension features simply won't be possible (including some features that are crucial to security/privacy). Which means we have to actively contribute. By properly testing WebExtensions, providing feedback to extension developers, filing Mozilla bug reports, voting for bug reports, contributing some code, etc. Make it a New Years resolution.
WebExtensions...
WebExtensions Wiki: https://wiki.mozilla.org/WebExtensions
WebExtensions MDN: https://developer.mozilla.org/en-US/Add-ons/WebExtensions
Info & Feedback...
Add-ons 2017 Planning: https://wiki.mozilla.org/Add-ons/2017
Release Calendar: https://wiki.mozilla.org/RapidRelease/Calendar:
Add-ons Dev Comms: https://wiki.mozilla.org/Add-ons/developer/communication
Add-ons Contributing: https://wiki.mozilla.org/Add-ons/Contribute
Dev-addons: https://mail.mozilla.org/listinfo/dev-addons
Add-ons Forum: https://discourse.mozilla-community.org/c/add-ons
Add-ons Blog: https://blog.mozilla.org/
Related:
http://www.ghacks.net/2016/11/24/firefox-will-only-support-web-extensions-by-the-end-of-2017/
http://www.ghacks.net/2016/11/26/classic-theme-restorer-may-be-dead-by-the-end-of-2017/
http://forums.mozillazine.org/viewtopic.php?p=14721955#p14721955
Firefox moving to WebExtensions exclusively by the end of 2017
Userlevel 7
+56
Userlevel 7
+54
Thank you Daniel, interesting but a lot of reading to do now.
Userlevel 7
+56
True but with only 13 months to go..... time flies.
Daniel 😉
Daniel 😉
Userlevel 7
Interesting article, Daniel...thanks for posting.
Have to say that on the face of it the Mozilla new approach seems a little insular, if not parochial, if they are going to be forcing the use of an API that will be "Without which some extension features simply won't be possible (including some features that are crucial to security/privacy)".
I presume that they are looking to make Firefox inherently more secure but in doing so may open up more potential malware vectors. Hmmm...will be interesting to see how this pans out.
Have to say that on the face of it the Mozilla new approach seems a little insular, if not parochial, if they are going to be forcing the use of an API that will be "Without which some extension features simply won't be possible (including some features that are crucial to security/privacy)".
I presume that they are looking to make Firefox inherently more secure but in doing so may open up more potential malware vectors. Hmmm...will be interesting to see how this pans out.
Userlevel 7
I don't have many Extensions on Firefox. Does this mean in 2017 I won't be able to use the following Extensions in Firefox?
Reply
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.