When BasicCompositor is used, BasicCompositor does not use CompositorWindow.
Differential Revision: https://phabricator.services.mozilla.com/D61345
--HG--
extra : moz-landing-system : lando
This is another one which is included everywhere. If the OOL call mattered we
could move these to a different header or something, but I suspect it won't.
Differential Revision: https://phabricator.services.mozilla.com/D62173
--HG--
extra : moz-landing-system : lando
nsPresContext.h is only used for unit conversion, which can be done by Units.h
in a similar fashion.
PresShell.h was needed for some capturing-content stuff which can be moved out
of line.
Differential Revision: https://phabricator.services.mozilla.com/D62170
--HG--
extra : moz-landing-system : lando
And fix a bunch of fallout as we now don't include nsDocShell.h everywhere.
Differential Revision: https://phabricator.services.mozilla.com/D62169
--HG--
extra : moz-landing-system : lando
Mostly what I was seeing come up in the .deps files from my object directory
which sounded feasible.
Differential Revision: https://phabricator.services.mozilla.com/D62167
--HG--
extra : moz-landing-system : lando
This avoids including nsFont.h and a bunch of other stuff in nsPresContext.h
Differential Revision: https://phabricator.services.mozilla.com/D62166
--HG--
extra : moz-landing-system : lando
We include it everywhere because it's included from gfxTypes.h.
This should avoid including all the generated bindings _everywhere_.
Differential Revision: https://phabricator.services.mozilla.com/D62174
--HG--
extra : moz-landing-system : lando
When ToolbarKeyboardNavigator initializes, it sets aria-hidden and adds a focus listener on toolbartabstop elements.
This is necessary for proper functionality of toolbar keyboard navigation.
However, widgets can be dynamically added by CustomizableUI after ToolbarKeyboardNavigator initializes.
The search bar is one such widget and it does contain toolbartabstop elements.
We now watch for this and initialize any toolbartabstop elements inside added widgets.
Differential Revision: https://phabricator.services.mozilla.com/D62178
--HG--
extra : moz-landing-system : lando
All of these call sites were unnecessarily converting nsIPrincipal* => IPC::Principal => nsIPrincipal*.
Differential Revision: https://phabricator.services.mozilla.com/D62327
--HG--
extra : moz-landing-system : lando
clang-10 hits a -Werror in IPDL headers about Principal's copy constructor not being explicitly defined. We could go and fix that constructor, but in light of bug 1443956, I'm guessing it's not really a bad thing to have a discouragement against Principal when nsIPrincipal is now usable directly.
Differential Revision: https://phabricator.services.mozilla.com/D62284
--HG--
extra : moz-landing-system : lando
The alternative code path was unused (as demonstrated by the presence of
`manifestdestiny` package). Remove that code path, so we can fail with a better
error message, if we don't have the right path to the requirements file.
Differential Revision: https://phabricator.services.mozilla.com/D62339
--HG--
extra : moz-landing-system : lando
The alternative code path was unused (as demonstrated by the presence of
`manifestdestiny` package). Remove that code path, so we can fail with a better
error message, if we don't have the right path to the requirements file.
Differential Revision: https://phabricator.services.mozilla.com/D62338
--HG--
extra : moz-landing-system : lando
Suppressing blur events prevents accessibility from firing focus events correctly when dismissing file picker dialogs.
This code was originally added in bug 68454 to fix a crash when bringing up a file picker dialog from the context menu on a window which calls self.close() on blur.
However, this crash can no longer be reproduced, so the code isn't needed any more.
Differential Revision: https://phabricator.services.mozilla.com/D62182
--HG--
extra : moz-landing-system : lando
This change ensures that we always remember to add a text track to media element's track list.
Differential Revision: https://phabricator.services.mozilla.com/D61666
--HG--
extra : moz-landing-system : lando
This telemetry records, for each toplevel window, the relationship between the
actual fission-enabled status of the window, and the "fission.autostart" pref.
This takes the form of a categorized telemetry histogram with the following
keys:
* EnabledByAutostart: useRemoteSubframes == true fission.autostart == true
* EnabledByUser: useRemoteSubframes == true fission.autostart == false
* DisabledByAutostart: useRemoteSubframes == false fission.autostart == false
* DisabledByUser: useRemoteSubframes == false fission.autostart == true
'DisabledByUser' helps indicate useful information such as how often fission
testers need to open non-fission windows due to breakage, while
'EnabledByAutostart' and 'EnabledByUser' helps give a better image of how many
people are testing fission.
Differential Revision: https://phabricator.services.mozilla.com/D61927
--HG--
extra : moz-landing-system : lando