Since background threads get shut down near `xpcom-shutdown-threads`,
there's no need to have `WebCryptoThreadPool` anymore; we can rely on
the background thread dispatching to fail to dispatch our task as
appropriate.
Differential Revision: https://phabricator.services.mozilla.com/D47006
--HG--
extra : moz-landing-system : lando
This will raise the high water mark of a parse, because we hold onto a copy of
the CharBuffer. There's a hard upper limit of the memory increase possible of
2x, where the parse consists almost entirely of BigInt literals, but,
nevertheless, this could be impactful on code that uses BigInt literals
extensively.
This patch also teaches FoldConstants how to tell if a BigInt is zero
without allocating the actual BigInt.
Differential Revision: https://phabricator.services.mozilla.com/D45256
--HG--
extra : moz-landing-system : lando
It's nicer to have everything in one place, and because we support
clang-cl, we can have a single definition for the error flag too.
Differential Revision: https://phabricator.services.mozilla.com/D45705
--HG--
extra : moz-landing-system : lando
I think most of them should not be needed after bug 1561450. From our discussion
at TPAC in https://github.com/w3c/csswg-drafts/issues/4239, there should be no
reason not to do this unless we find fallout.
We need to enable the pref in tests that test these particular heuristics of
course.
Differential Revision: https://phabricator.services.mozilla.com/D47315
--HG--
extra : moz-landing-system : lando
That is, for the multicol container of depth two and more, we lay them
out by using "column-fill:auto" and "column-count:1".
I've check bug 725376 comment 9 for the previous approaches. Thanks to
bug 1555818, this solution is feasible because the fragmentation with
"column-fill:auto" is now possible.
Differential Revision: https://phabricator.services.mozilla.com/D47011
--HG--
extra : moz-landing-system : lando
Change the taskcluster max-run-time for mochitests and reftests to use the
defaults, now that android tests no longer run anywhere near 7200 seconds.
(Also noticed some unrelated tc configuration that is obsolete - tidied that.)
Also remove the special 600 second reftest timeout for android debug reftests.
Differential Revision: https://phabricator.services.mozilla.com/D47301
--HG--
extra : moz-landing-system : lando
This will raise the high water mark of a parse, because we hold onto a copy of
the CharBuffer. There's a hard upper limit of the memory increase possible of
2x, where the parse consists almost entirely of BigInt literals, but,
nevertheless, this could be impactful on code that uses BigInt literals
extensively.
This patch also teaches FoldConstants how to tell if a BigInt is zero
without allocating the actual BigInt.
Differential Revision: https://phabricator.services.mozilla.com/D45256
--HG--
extra : moz-landing-system : lando
Using git-archive for the fetch task means that we don't get the
submodules of a git repository included in the archive. There isn't a
straightforward way to get submodules from a bare repo included with
git-archive, so instead we can simply clone & checkout with
--recurse-submodules and then use a standard tar command to bundle up
the tree.
Adding --recurse-submodules to the commands has no effect on a repo
without submodules, so we can add it to all invocations for simplicity.
Differential Revision: https://phabricator.services.mozilla.com/D46827
--HG--
extra : moz-landing-system : lando
The last update of the CodeMirror library introduced new
CSS selectors in the css file with a greater specificity than
they used to, which means the color property we set in our
themes css files weren't applied.
We change the selectors in our theme files so they are more
specific than the ones in codemirror's css file.
Differential Revision: https://phabricator.services.mozilla.com/D47291
--HG--
extra : moz-landing-system : lando
Intent to unship: https://groups.google.com/forum/#!topic/mozilla.dev.platform/JnJVGTmIwPE
- Introduce a new preference option mathml.deprecated_alignment_attributes.disabled()
to disable alignment attributes for mfrac/munder/mover/munderover elements.
- Disable the attributes in Nightly and when running WPT tests.
- Enable the attributes in other channels but add a counter and deprecation warning.
- Remove failure expectation for WPT test frac-numalign-denomalign-001.html for mfrac
- Add new WPT test for underover-legacy-align-attribute-001.html for munder/mover/munderover
- Enable the attributes for MathML reftests checking these attributes.
- Disable numalign/denomalign test for Mochitest test_bug975681.html when the attributes
are disabled.
Differential Revision: https://phabricator.services.mozilla.com/D46712
--HG--
extra : moz-landing-system : lando
We could use RLIMIT_DATA here, but that seems to have slightly different semantics
and it seems best to just stick to use RLIMIT_AS for this heuristic.
Differential Revision: https://phabricator.services.mozilla.com/D47267
--HG--
extra : moz-landing-system : lando
To avoid duplicating information, the comment about lock ordering in
APZCTreeManager.h is also updated to point to the documentation.
Differential Revision: https://phabricator.services.mozilla.com/D47146
--HG--
extra : moz-landing-system : lando
