Requires Firefox, Chrome or Opera. Because it uses TextEncoder.
WebExtensions are becoming the standard for add-on development in Firefox. At the same time, multiprocess Firefox (aka Electrolysis, or e10s) is also rolling out. These changes impact developers of XUL/XPCOM and SDK add-ons (some more than others).
The tool below will tell you which technology your add-on uses and what your options are for staying compatible. A comprehensive collection of resources is available to help you through the transition if you are affected.
You will need your add-on guid, which is found in one of the following places:
install.rdfof your add-on
package.jsonfor an SDK add-on
Manage My Submissionsand select the add-on, then scroll down to
Your add-on guid should be one of the following:
Probably not a valid add-on id. That is the id of one of the applications such as Firefox or Thunderbird and not your add-on.
We think this is an SDK add-on using legacy APIs. These APIs will be deprecated once WebExtensions become the standard for add-on development. More Information
We think this is an SDK add-on using high level APIs. Your add-on will probably continue to work without problems, but we recommend you start looking into WebExtensions.
Also, please note that as of March 2016, SDK add-ons that were built using the cfx tool (Jetpack version 1.17 and lower) need to be repackaged using the newer jpm tool in order to continue being compatible with Firefox. More Information
We think this add-on is using XUL or XPCOM. We recommend that you start looking into the SDK or WebExtensions as soon as possible. More Information
We couldn't find your add-on id in our list of add-ons. That just means that we haven't explicitly looked it up for compatibility. More Information
Source of this tool is on github.