gecko-dev/dom/browser-element
Emilio Cobos Álvarez 3987c781d0 Bug 1635914 - Move active flag handling explicitly to BrowsingContext. r=nika
And have it mirror in the parent process more automatically.

The docShellIsActive setter in the browser-custom-element side needs to
be there rather than in the usual DidSet() calls because the
AsyncTabSwitcher code relies on getting an exact amount of notifications
as response to that specific setter. Not pretty, but...

BrowserChild no longer sets IsActive() on the docshell itself for OOP
iframes. This fixes bug 1679521. PresShell activeness is used to
throttle rAF as well, which handles OOP iframes nicely as well.

Differential Revision: https://phabricator.services.mozilla.com/D96072
2020-12-11 15:43:19 +00:00
..
BrowserElementChild.js Bug 1635914 - Move active flag handling explicitly to BrowsingContext. r=nika 2020-12-11 15:43:19 +00:00
BrowserElementChildPreload.js Bug 1635914 - Move active flag handling explicitly to BrowsingContext. r=nika 2020-12-11 15:43:19 +00:00
BrowserElementParent.jsm Bug 1635914 - Move active flag handling explicitly to BrowsingContext. r=nika 2020-12-11 15:43:19 +00:00
BrowserElementPromptService.jsm
components.conf
moz.build Bug 1654103: Standardize on Black for Python code in `mozilla-central`. 2020-10-26 18:34:53 +00:00
nsIBrowserElementAPI.idl