Firefox 37 will be released on March 31st. Here’s the list of changes that went into this version that can affect add-on compatibility. There is more information available in Firefox 37 for Developers, so you should also give it a look.
General
- Remove
String.prototype.quote
. - Implement
nsIContentPolicy.shouldProcess
for plugin resource loads. Content policy implementations should expect more function calls because of this. Make sure you filter out calls you don’t need as early as possible. - Convert to Downloads.jsm in Firefox for Android.
- Update: “Allow pages to choose their own colors” does not work with high contrast windows themes. I learned about this change after the release (sorry). This affects add-ons that use the “browser.display.document_color_use” preference.
XPCOM
- Remove
nsIDownloadManagerUI
from Firefox for Desktop. - Remove
nsISiteSecurityService.shouldIgnoreHeaders
and implementation.
New!
- JavaScript sources loaded in chrome URIs are now visible. This change means that the debugger now displays scripts for content that comes from chrome: URLs, like about: pages and certain add-on UI.
Please let me know in the comments if there’s anything missing or incorrect on these lists. If your add-on breaks on Firefox 37, I’d like to know.
The automatic compatibility validation and upgrade for add-ons on AMO will probably happen in mid-March, so keep an eye on your email if you have an add-on listed on our site with its compatibility set to Firefox 36.
Kohei Yoshino
wrote on
Jorge Villalobos
wrote on
kevin007
wrote on
Dwan
wrote on
jus
wrote on
Thor
wrote on