Confirmed users
1,158
edits
Add-ons/Future of Bootstrap: Difference between revisions
no edit summary
(Created page with "== The future of bootstrapped addons == With the deprecation of legacy extensions in Firefox 57, we have eliminated most uses of bootstrapped extensions in Firefox. System a...") |
No edit summary |
||
| Line 1: | Line 1: | ||
== The future of bootstrapped addons == | == What == | ||
Third party add-ons can only be a bootstrapped add-on. However "internal" Mozilla add-ons can be bootstrapped with special signing. We intend to remove bootstrapped add-ons completely from the Firefox ecosystem. | |||
See [[Add-ons/InternalSigning|Internal Signing]] for information on this internal signing process. | |||
== Why == | |||
Bootstrapped add-ons represent use of a legacy technology. The tools and paths are becoming increasingly deprecated and broken. Bootstrapped add-ons can easily be broken every release and make updating Firefox. | |||
Mozilla should use, as much as possible, the same tools as everyone else. This will drive WebExtensions forward for third party and internal consumers. | |||
== How == | |||
Working with the teams that have bootstrapped add-ons we'll work with them to do one of the following, depending upon what makes the most sense: | |||
* Move the custom code into Firefox. | |||
* Move the custom code into a WebExtension Experiment bundled with the WebExtension {{Bugzilla|1364976}}. | |||
* Move the custom code into Firefox as a WebExtension API. | |||
* Move the custom code into Firefox as a WebExtension API available only to Mozilla {{Bugzilla|1280235}}. | |||
A working group has been established to work on this and we'll be sending out some documentation and plans shortly. | |||
== Notes == | |||
=== The future of bootstrapped addons === | |||
With the deprecation of legacy extensions in Firefox 57, we have eliminated most uses of bootstrapped extensions in Firefox. System add-ons and other special cases such as Shield extensions can still be written as bootstrapped extensions. In the near term, we hope to make it possible for these extensions to be written as WebExtensions (with things that aren't suitable for public WebExtension APIs accessed through private APIs or WebExtension experiments). But in the mean time, other changes in Firefox have the potential to break bootstrapped extensions. This page is meant to document some of the problems that authors of bootstrapped extensions should be aware of. | With the deprecation of legacy extensions in Firefox 57, we have eliminated most uses of bootstrapped extensions in Firefox. System add-ons and other special cases such as Shield extensions can still be written as bootstrapped extensions. In the near term, we hope to make it possible for these extensions to be written as WebExtensions (with things that aren't suitable for public WebExtension APIs accessed through private APIs or WebExtension experiments). But in the mean time, other changes in Firefox have the potential to break bootstrapped extensions. This page is meant to document some of the problems that authors of bootstrapped extensions should be aware of. | ||