* @import rather than %include stylesheets in each platform's browser.css
* Remove the inc.css suffix for @imported files
* browser.inc.css becomes browser-shared.css
* Move shared @imports to browser-shared.css
* panelUI.inc.css becomes panelUI-shared.css
* download/indicator.inc.css becomes download/indicator.css and is @import-ed.
* addons/extension-controlled.inc.css becomes addons/extension-controlled.css and is @import-ed
* places/places-tooltip.inc.css becomes places/places-tooltip.css and is @import-ed
* urlbar/dynamicResults.inc.css becomes urlbar-dynamic-results.css and is @import-ed from urlbarView.css
* Remove preprocessing flags from css resources in jar.inc.mn that no longer contain any preprocessor directives
Differential Revision: https://phabricator.services.mozilla.com/D140275
This doesn't change behavior but makes some code a bit nicer to read and
documents some of the code that wasn't obvious otherwise.
Differential Revision: https://phabricator.services.mozilla.com/D141236
The presenting issue is that each background task's audio session is
user-visible via various Windows UIs that display "volume controls" or
"volume mixers"; this avoids that.
Differential Revision: https://phabricator.services.mozilla.com/D141101
There are a few ways that we could test this. We could use the
profiler and "File IO" markers, a la
https://searchfox.org/mozilla-central/source/browser/base/content/test/performance/browser_startup_content_mainthreadio.js.
This would profile content that is transient, which could be good or
bad -- temporary files for atomic writes would show up for example.
But in fact there are profile contents created after the profiler is
shut down (including `Telemetry.ShutdownTime.txt`), so this approach
isn't sufficient.
Therefore we do the simpler thing: we simply don't remove the
temporary profile directory after the background task exits.
Differential Revision: https://phabricator.services.mozilla.com/D139909
Now that we're using `sysconfig` instead of `distutils`, our `purelib`
and `platlib` paths should correctly point to python environment paths
without a spurious `local/` component at their roots.
Differential Revision: https://phabricator.services.mozilla.com/D140871
Depending on the subprocesses created (such as if
`--with-ccache=sccache` is set), `./mach configure` may hang.
More details about why this is is documented in bug 1753797.
The workaround is to lean on the standard library to stream-and-format
output, rather than our existing `ProcessHandler` code.
Though this still streams both `stdout` and `stderr` in real-time, I saw
some ordering differences between the two streams locally. I don't yet
have a reason to believe that these differences are harmful or otherwise
incorrect.
Differential Revision: https://phabricator.services.mozilla.com/D141028
For local running it's inconvenient to have to manually download or
build geckodriver, so if we don't already have a build then download
the latest stable release from GitHub. This shouldn't affect CI since
we always have a build in that case.
Differential Revision: https://phabricator.services.mozilla.com/D141244
This hints at an actual case:
When enabling telemetry and _quickly_ closing the browser afterwards,
telemetry might get enabled and trigger a shutdown ping, but will not
have initiated setting a new client ID.
This is unlikely to be hit for any real-user scenario: Toggling
telemetry requires UI interaction (either in the preferences or in
about:config) and thus is unlikely to be followed by a shutdown quickly
enough.
Differential Revision: https://phabricator.services.mozilla.com/D140965
RecvPCamerasConstructor() is used because IPC messages cannot be sent from
AllocPCamerasParent() because SetManagerAndRegister() has not been called to
change mLinkStatus to Connected.
Differential Revision: https://phabricator.services.mozilla.com/D140022
This test runs a lot of JS and triggers a lot of unrelated assertions,
some of which are fatal. The test added in bug 1755790 is much simpler
and a better fit for providing test coverage for the patches in bug
1749190.
Differential Revision: https://phabricator.services.mozilla.com/D141177
