Mozilla raised the sword over XPCOM interfaces used by XUL extensions
Posted: 2017-07-31, 17:54
They are definitely going to emasculate the core browser code
Here is the short list of the corresponding bugs based on the current state of bug #1347507:

Here is the short list of the corresponding bugs based on the current state of bug #1347507:
- Remove support for Date.prototype.toLocaleFormat
- Decommission nsIDownloadManager
- Stop building nsIEntityConverter and its property files on mobile
- Remove SpiderMonkey support for ECMAScript for XML for-each
- Remove SpiderMonkey support for JS1.7 legacy generators
- Remove nsIProgrammingLanguage
- Remove nsIStackFrame::language
- Remove nsISaveAsCharset & nsSaveAsCharset from m-c
- Get addons to stop using DOM_OBJECT classinfo
- Get rid of nsIUnicodeNormalizer interface
- Deprecate nsIScriptableDateFormat
- Remove nsIJSON
- Remove extensions.ini
- Remove nsIScriptableUnicodeConverter
- Remove nsIConverterInputStream
- Remove nsIConverterOutputStream
- Deprecate nsIScriptableInputStream and nsIStringInputStream
- Remove nsILocaleService
- Remove UI, extension, and child_process modules
- Remove FUEL
- Disable named property object visibility on Xrays across the board once 57 ships
- Deprecate and remove nsLocaleService, nsILocaleService, nsLocale, and nsPosixLocale
- Remove nsISimpleContentPolicy
- Remove support for SourceHook
- Remove nsIPrefBranch2 and nsIPrefBranchInternal
- nsIDOMWindow and nsIDOMWindowInternal
- Remove nsILocalFile
- Try to remove some shutdown observer notifications
- Remove Promise.jsm
- Remove nsHTMLEntities.cpp
- PrintPreview should only be allowed on nsIWebBrowserPrint when retrieved through the docshell.
- Remove nsPIEditorTransaction
- Remove Locale.jsm
- Remove support for "skin" chrome registration after removing support for complete themes