If your add-on breaks on Firefox 43, I’d like to know. Please let me know in the comments if there’s anything missing or incorrect on these lists. There’s a preference that turns signing enforcement off ( in about:config), but the current plan is to drop the preference in Firefox 44. Unsigned add-ons won’t install and will be disabled by default.
This is the first version of Firefox that will enforce signing. However, these changes should only break compatibility if you are interacting with these components on a binary level. A security fix made some changes to the following interfaces: nsIDocShell, nsIDocShellLoadInfo, nsISHEntry. This makes changes in nsIQuotaManager and nsIUsageCallback. Use origin attribute in nsIUsageCallback. Give the canvas documentation a look for possible alternatives. This was a non-standard, internal use function, but a few add-ons used it. Remove nsIDOMHTMLCanvasElement::MozFetchAsStream(). Paraphrasing: any content loaded into a webpage needs to have contentaccessible=yes, no matter how it is loaded, which means that add-ons loading XBL into content will probably need to add it. Comment 64 explains what this has to do with add-ons. Use channel->ascynOpen2 dom/xbl/nsXBLService.cpp. There is more information available in Firefox 43 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 43 will be released on December 15th.
0 kommentar(er)
