Not just that, but soon CTR will stop functioning as well.Ī disappointment and a poor judgement being passed only to introduce a lack-luster “substitute” that only compliments so much of what we want. Tags: compatibility, developers, documentation, e10s, firefox 55, webextensionsĬategories: compatibility, developers, documentation 6 responses
The automatic compatibility validation and upgrade for add-ons on AMO will happen in a few weeks, so keep an eye on your email if you have an add-on listed on our site with its compatibility set to Firefox 54. We’d like to know if your add-on breaks on Firefox 55. Let me know in the comments if there’s anything missing or incorrect on these lists. This can affect add-ons that use nsICryptoHash or nsICryptoHMAC. Avoid using NSS Base64 functions in PSM.Compile subscript loader scripts with noScriptRval by default.Remove nsIScreenManager.systemDefaultScale.This change touches many interfaces, but most adds an optional preferred width argument to some functions (see 1 and 2). Move favicons blobs out of places.sqlite to their own database.Now the developers are considering alternatives to avoid add-on issues. As you can see if you follow the link, the bug was reopened. This can affect add-ons that load custom URLs using special protocols (like about:). Expose result principal URL (“final channel URL”) on LoadInfo.Disable loading remote jars by default.Get rid of UIEvent.isChar because no other browsers support it.This could affect some add-ons that use the hidden DOM window hack. Remove the hiddenwindow special case in CheckLoadURIWithPrincipal.This mainly affected tab add-ons that use or override openURIInFrame and related functions. Replace the sNextTabParent setup with something more robust.Remove Java Addons support from Fennec.The main change of this bug that could affect developers is that Panel views are loaded when the panel is first shown, rather than when it is created. Also, Firefox 55 is the first version to move directly from Nightly to Beta after the removal of the Aurora channel. Recently, we turned on a restriction on Nightly that only allows multiprocess add-ons to be enabled. Also, if you haven’t yet, please read our roadmap to Firefox 57. There is more information available in Firefox 55 for Developers, so you should also give it a look. Here’s the list of changes that went into this version that can affect add-on compatibility. Firefox 55 will be released on August 8th.