bug 1348713 - ensure CT information is set in the case of session resumption r?jcj MozReview-Commit-ID: 7fLnMu9f1kC

Backed out changeset 31172c0751dd for investigating Bug 1349208 on a CLOSED TREE

No bug, Automated blocklist update from host bld-linux64-spot-094 - a=blocklist-update

No bug, Automated HPKP preload list update from host bld-linux64-spot-094 - a=hpkp-update

No bug, Automated HSTS preload list update from host bld-linux64-spot-094 - a=hsts-update

Bug 1345991 - SVG Image Elements aren't displayed in the Page Info view media list. r?florian MozReview-Commit-ID: LlHwl2Kn1Vk

Bug 1256472 - Make ShutdownLeaksCollector do more aggressive GCing and CCing to avoid erroneous shutdown leak reports in tests. r?mccr8 With bug 1256472 fixed, we have greater probability of out-of-process browsers being in the midst of teardown and destruction when tests complete. There's already TabDestroyObserver in the parent process making sure that the TabParent's are properly cleaned up, but we need to be more aggressive about clearing out remaining nsIDOMWindow's and DocShells in the content processes. This change more or less mirrors what's already going on in browser-test.js. MozReview-Commit-ID: FZnNLpbfTEY

Bug 1256472 - Account for the possibility that the selectedTab has not yet presented when initting async tab switcher. r?billm MozReview-Commit-ID: 1mXffrdUBOE

Bug 1256472 - Make sure checkEmptyPageOrigin checks the browser documentURI for about:blank along with the currentURI. r?Gijs checkEmptyPageOrigin was only checking the currentURI on the passed browser for about:blank, but sometimes the currentURI isn't the whole picture. For example, SessionStore, after restoring a window, can cause a number of blank tabs to start to load, be cancelled, and have their history replaced. This results in a bunch of unrestored background tabs that appear to have currentURI set to the URI that the tab will be sent to once restored, but a null content principal, since the original about:blank load was stopped before it could complete. We side-step this issue by checking both the currentURI and the documentURI for about:blank when comparing against the null principal for checkEmptyPageOrigin. MozReview-Commit-ID: Kzm0MthLqVM

Bug 1256472 - When restoring a window, initialize each browser tab as remote if possible. r?mikedeboer Originally, we were forcing these restored background tabs to be non-remote by default. This was because we didn't want them to show the crashed tab favicon nor show about:tabcrashed if the user hadn't restored them before. Bug 1241459 added infrastructure that makes it possible to put crashed background tabs into the "restore on demand" state again, without showing about:tabcrashed or showing the crashed tab favicon. This means we should be able to restore tabs in the content process again which should take some load off of the parent process during session restore, which is good for perceived performance. Note that if the content process does crash, the background tabs are then loaded in the parent process. Restoring them on demand will then do the remoteness flip. MozReview-Commit-ID: 1mWe0td6geB

Bug 1256472 - Add a reason to the restoreTabContent function and message. r?mikedeboer, Gijs This helps differentiate restorations that were caused by navigateAndRestore, as opposed to SessionStore having set state via setBrowserState, setWindowState, or setTabState. MozReview-Commit-ID: DEEbKLh7f7p

Bug 1302702 - Remove from ext-backgroundPage any code that uses the AddonManager object. The background page do not need to use the AddonManager to set its preferred debugging global anymore (and it would not be able to use it from the extension child process). MozReview-Commit-ID: 2IAxvCjDKvl

Bug 1302702 - Add tests to check that ExtensionDebuggingUtils is cleaned up when the addon debugger is closed. MozReview-Commit-ID: GZT0U1kNwr3

Bug 1302702 - Make WebExtension Addon Debugging oop-compatible. This patch applies all the changes needed to the devtools actors and the toolbox-process-window, to be able to debug a webextension running in an extension child process (as well as a webextension running in the main process). The devtools actor used to debug a webextension is splitted into 3 actors: - the WebExtensionActor is the actor that is created when the "root.listTabs" RDP request is received, it provides the addon metadata (name, icon and addon id) and two RDP methods: - reload: used to reload the addon (e.g. from the "about:debugging#addons" page) - connectAddonDebuggingActor: which provides the actorID of the actor that is connected to the process where the extension is running (used by toolbox-process-window.js to connect the toolbox to the needed devtools actors, e.g. console, inspector etc.) - the WebExtensionParentActor is the actor that connects to the process where the extension is running and ensures that a WebExtensionChildActor instance is created and connected (this actor is only the entrypoint to reach the WebExtensionChildActor, and so it does not provide any RDP request on its own, it only connect itself to its child counterpart and then it returns the RDP "form" of the child actor, and the client is then connected directly to the child actor) - the WebExtensionChildActor is the actor that is running in the same process of the target extension, and it provides the same requestTypes of a tab actor. By splitting the WebExtensionActor from the WebExtensionParentActor, we are able to prevent the RemoteDebuggingServer to connect (and create instances of the WebExtensionChildActor) for every addon listed by a root.listAddons() request. MozReview-Commit-ID: L1vxhA6xQkD

Bug 1302702 - Provide an ExtensionDebuggingUtils object from ExtensionParent.jsm. This change prepare the WebExtensions internals to the changes applied to the addon debugging facilities in the other patches from this queue. In ExtensionParent.jsm, a HiddenXULWindow helper class has been refactored out of the HiddenExtensionPage and then reused by both HiddenExtensionPage and the new ExtensionDebuggingUtils object. The ExtensionDebuggingUtils object provides the utility methods used by the devtools actors related to the addon debugging, which are used to retrieve an "extension process browser XUL element" (a XUL browser element that has been configured by ExtensionDebuggingUtils to be used to connect the devtools parent actor to the process where the target extension is running), and then release it when it is not needed anymore (because the developer toolbox has been closed and all the devtools actors destroyed). The ExtensionDebuggingUtils object used the HiddenXULWindow class to lazily create an hidden XUL window to contain the "extension process browser XUL elements" described above (and the HiddenXULWindow istance is then destroyed when there is no devtools actor that is using it anymore). MozReview-Commit-ID: 31RYQk1DMvE

Bug 1348900 - Deprecate NewTimerCallback. r?kats MozReview-Commit-ID: 9Ap24GZ8M4

Bug 1342863 - (Part 8) DocGroup labeling for timer callback in nsRefreshDriver. r?dholbert MozReview-Commit-ID: DP7WFkvlrPq

Bug 1342863 - (Part 7) DocGroup labeling for timer callabck in nsPresContext. r?dholbert MozReview-Commit-ID: Jhl2FVc8PRd

Bug 1342863 - (Part 6) DocGroup labeling for timer callback in PresShell. r?dholbert MozReview-Commit-ID: 9gfiu9DN2aT

Bug 1342863 - (Part 5) DocGroup labeling for runnables dispatched by NS_DispatchTo(Main|Current)Thread in nsRefreshDriver. r?dholbert MozReview-Commit-ID: CzddDOagdfZ