This patch exposes the add-on manager web API behind a static pref
instead of a build flag. The pref allows embedders to expose the API to
the usual list of allowed domains (AMO only, except for testing).
Differential Revision: https://phabricator.services.mozilla.com/D179968
- Prior to this change, we allowed any timer *except* the first to fire early. Being woken up
slightly before our first timer is due was resulting in a lot of "wasted" wake-ups (where we wake
up and do nothing other than go back to sleep).
- This change results in waking up TimerThread 10% less frequently in my test case of watching a
YouTube video.
- Made the allowed early firing tolerance be a constant value rather than calculated at run-time.
- Also cleaned up some includes.
Differential Revision: https://phabricator.services.mozilla.com/D184017
I didn't find a single GTK theme that drew something useful for this:
* The container appearance isn't needed. It is a hack needed to get the
right styles for the native checkbox, but that's it, we don't need to
expose it to CSS.
* The label appearance was meant to draw the focus outline but since it
didn't work reliably we've been doing it manually since seven years
ago (see bug 582951 and bug 1312169).
Other platforms also don't use these so this simplifies the code a bit.
Depends on D185279
Differential Revision: https://phabricator.services.mozilla.com/D185286
Test tasks have contain a ReadOnlyDict from mozbuild.util (under
task["extra"]["test-setting"]) that PyYAML's safe_dump will not serialize
as it has no way of representing it.
TGDumper is a subclass that converts ReadOnlyDicts to regular dicts, and then
dumps accordingly. The assumption is that dumping a taskgraph to YAML is useful
for debugging, round-trips back to a taskgraph object are unnecessary, and
it's acceptable to lose the "read-only" status of these objects when serialized.
(This is what happens when serialized to JSON.)
Another quirk of dumping to YAML is objects are aliases and de-duplicated. This
results in things like `test-setting: *id1337`, which is a reference to
`test-setting: &id1337` (and the definition that follows). That's not too
readable, and again since round-trips are not needed TGDumper disables the use
of these aliases.
Differential Revision: https://phabricator.services.mozilla.com/D185239
Normally the `taskgraph_decision` code is not run outside of CI, but when using
`mach test-action-callback` locally it is used. The hardcoded path is problematic
when doing so.
Differential Revision: https://phabricator.services.mozilla.com/D185223
Bug 1839262 converted the gtest harness to use raw subprocess, but we can get
the same functionality more simply now with mozprocess.run_and_wait.
Differential Revision: https://phabricator.services.mozilla.com/D185208
* whitespace-trim-*: These tests are testing whitespace trimming in
token elements but that's not described in MathML Core. Move them
into internal WPT tests.
* table-width-1,2,3,4: These tests verify that the intrinsic width
is properly calculated so that MathML content don't overflow in
tables. One of them is related to whitespace trimming, so
extract it to internal WPT test.
* test_bug330964.html: Convert this to a testharness test and
move it into internal WPT test (this is testing mtable
attributes that are not part of MathML Core).
* semantics-4: Restore the original testcase and move it into
internal WPT test with a failure annotation for now (as written
it uses mtable@width attribute which is not part of MathML Core
anyway). For details, see bug 1846930.
* dir-6a: This was introduced in bug 330964 and involves table
attributes that are not part of MathML Core.
* css-spacing-1.html: This was introduced by bug 1187673 but is already
covered by default-properties-on-the-math-root.html.
* columnlines/rowlines: Tests for columnlines/rowlines attributes that
are not part of the current version of MathML core. Move them to
mozilla/tests/mathml/tables. Use Ahem for rowlines/columnlines-3*
to make them more robust per bug 1309426.
* mstyle-2: extract the case for mtable@align test to internal
WPT mstyle-align.html since align is not part of MathML Core.
Differential Revision: https://phabricator.services.mozilla.com/D185270
This patch removes the automation check from the parent to the child,
since we don't want to load more scripts into the child process.
Differential Revision: https://phabricator.services.mozilla.com/D185295
The move to `from-deps` changed the dependency edge name from `build` to
`system-symbols`. Apparently this is what the first path segment in an
`artifact-reference` is.
We should probably change the separator to a `:` or something here.
Differential Revision: https://phabricator.services.mozilla.com/D185297
Tryserver says this fails on Linux, though it passes for me locally;
it depends whether we end up using subpixel positioning or not, which
in turn is dependent on a whole slew of factors. So marking as random
there. Other platforms look happy.
Depends on D184820
Differential Revision: https://phabricator.services.mozilla.com/D185294
Quantizing to quarter-pixel size is too coarse for extremely small sizes
(that will subsequently be scaled up, as here); it's also arguably finer
than needed at very large sizes. So instead of using a constant, this
patch makes us quantize the size by dropping the low bits of precision
from the mantissa, so that the quantization scales along with the size
being used.
Depends on D184819
Differential Revision: https://phabricator.services.mozilla.com/D184820
This is being triggered by a later patch that is adding new logging. I
believe this is all just because of initialization order.
Differential Revision: https://phabricator.services.mozilla.com/D185210
