Differential Revision: https://phabricator.services.mozilla.com/D156322

Differential Revision: https://phabricator.services.mozilla.com/D156321

Differential Revision: https://phabricator.services.mozilla.com/D156320

This is callable from JS, and nothing guarantees that style has been
updated properly before. Without this, my previous patch causes failures
in browser/base/content/test/tabdialogs/browser_tabdialogbox_focus.js,
because the nsDeckFrame used to listen to attribute changes
synchronously and now it's style-based, so if you moveFocus right after
revealing it we'd end up with the wrong answer.

Differential Revision: https://phabricator.services.mozilla.com/D157886

Differential Revision: https://phabricator.services.mozilla.com/D157861

Differential Revision: https://phabricator.services.mozilla.com/D157664

There's a comment below that says that we occasionally observe collector time
being larger than total time, so it's not safe to assert this.

Differential Revision: https://phabricator.services.mozilla.com/D157919

Backed out 11 changesets (bug 1788969, bug 1782400, bug 1777145) for causing bp-hybri bustages. CLOSED TREE

Backed out changeset 8acabb924ef7 (bug 1782400)
Backed out changeset e3d452e99f77 (bug 1782400)
Backed out changeset 5727bc4895d2 (bug 1777145)
Backed out changeset cf375034e2b8 (bug 1777145)
Backed out changeset a50fd5608d8d (bug 1777145)
Backed out changeset f24853cacd7a (bug 1777145)
Backed out changeset c714f3a35b11 (bug 1777145)
Backed out changeset 56682c253427 (bug 1788969)
Backed out changeset edaf37ffc49d (bug 1788969)
Backed out changeset d19caa9f062b (bug 1788969)
Backed out changeset 18b26912dc03 (bug 1788969)

Bug 1783406 - Provide a separate environment for the globals in recommended ESLint config r=Standard8

Differential Revision: https://phabricator.services.mozilla.com/D157665

Differential Revision: https://phabricator.services.mozilla.com/D157932

Differential Revision: https://phabricator.services.mozilla.com/D156350

Differential Revision: https://phabricator.services.mozilla.com/D156349

Bug 1777145 - Don't expose Wrap for WebIDL iterable iterator objects outside of binding code. r=edgar

Differential Revision: https://phabricator.services.mozilla.com/D156348

Differential Revision: https://phabricator.services.mozilla.com/D156347

Differential Revision: https://phabricator.services.mozilla.com/D156346

Differential Revision: https://phabricator.services.mozilla.com/D156345

Bug 1777145 - Expose the Wrap function for WebIDL iterable iterators through a template argument instead of as a function pointer member. r=edgar

Differential Revision: https://phabricator.services.mozilla.com/D156344

Implement the common steps for the next method from
https://webidl.spec.whatwg.org/#es-asynchronous-iterator-prototype-object in
a base class, that all async iterable iterator objects inherit from. Natives
that implement an async iterable only need to implement the "getting the
next iteration result" part in their GetNextPromise method. This means they
don't have to create the object according to "CreateIterResultObject"
themselves, but can just create promise and often resolve it with a native
value directly. We've switched to a special JS::Value to signal "end of
iteration", but that's hidden inside the
iterator_utils::ResolvePromiseForFinished helper.
The WebIDL parser now uses the right return type for the generated "next"
method, which means that any exceptions in the binding code itself will
actually be correctly converted to a rejected promise instead of being
rethrown.
This also uses a class for the generated iterable iterator that's not
exposed outside the binding code. No other code should create and/or
wrap these anyway.

Differential Revision: https://phabricator.services.mozilla.com/D156323

Differential Revision: https://phabricator.services.mozilla.com/D156322

Differential Revision: https://phabricator.services.mozilla.com/D156321

Differential Revision: https://phabricator.services.mozilla.com/D156320

Retain the full stall period in the main process; stall for only half as
long in all other processes.

Differential Revision: https://phabricator.services.mozilla.com/D157140

Refactor to allow specifying a potentially variable stall-count and
-time, rather than a binary stall/don't-stall cue.

No functional changes; this facility will actually be used in the next
commit.

Differential Revision: https://phabricator.services.mozilla.com/D157139

Sufficient data has been acquired to confirm that all-stall does indeed
increase the chance of a main-process OOM compared to just main-stall.

Revert to all-stall anyway, solely to simplify the next two commits.

Differential Revision: https://phabricator.services.mozilla.com/D157138

Add thread-safety annotations for a few of the mutexes in mozjemalloc.

Differential Revision: https://phabricator.services.mozilla.com/D157858

Bug 1773868 - - Increase wait time for obtaining video from android devices. r=perftest-reviewers,sparky

Differential Revision: https://phabricator.services.mozilla.com/D157829

Bug 1787809 - Secondary button arrow should be inline so responsive shows it more centered r=jprickett

Differential Revision: https://phabricator.services.mozilla.com/D156886

The last time we re-recorded the google-docs site, it had been updated to the canvas version. There is no reason to keep the separate google-docs-canvas page load test around.

Differential Revision: https://phabricator.services.mozilla.com/D157507

Differential Revision: https://phabricator.services.mozilla.com/D157863

Differential Revision: https://phabricator.services.mozilla.com/D157857

Differential Revision: https://phabricator.services.mozilla.com/D157923

Bug 1789468 - Add telemetry probe to measure from AsyncOpen to the transaction being added to the HttpConnectionManager r=necko-reviewers,kershaw

Collect this timing because it's on the critical path and may be slow in some scenarios.

Differential Revision: https://phabricator.services.mozilla.com/D157204

This will allow this function to eventually return an appropriate value
depending on whether or not content is skipped via `content-visibility:
auto`. This change also starts looking directly at whether
content-visibility is skipping content or not, which should make it
compatible with a future `content-visibility: auto` implementation.

Differential Revision: https://phabricator.services.mozilla.com/D157831

MathML Core specifies that operators containing a UTF-16 strings of
length 2 ending with U+0338 COMBINING LONG SOLIDUS OVERLAY or U+20D2
COMBINING LONG VERTICAL LINE OVERLAY should just use the properties of
the first character. This commit implements that behavior. It removes
obsolete entries that are superseded by this rule and modifies
updateOperatorDictionary.pl to ensure that no such entries are present.

Existing WPT test operator-dictionary-combining.html is already passing
after bug 1789583 because the operators tested use the default spacing.
So extend it to try operators with different spacing.

[1] https://w3c.github.io/mathml-core/#dfn-algorithm-to-determine-the-category-of-an-operator

Differential Revision: https://phabricator.services.mozilla.com/D157707

Bug 1790009, part 2 - Operator dictionary: Only accept UTF-16 strings of 1 or 2 characters. r=emilio

MathML Core specifies that operators containing a UTF-16 strings whose
length is not 1 or 2 should use the default properties [1]. This
commit removes the obsolete strings of length 3 from our operator
dictionary and tweak updateOperatorDictionary.pl to ensure it only
accepts strings of 1 or 2 characters. This also adds an early return
in LookupOperator to immediately fallback to default properties.

[1] https://w3c.github.io/mathml-core/#dfn-algorithm-to-determine-the-category-of-an-operator

Differential Revision: https://phabricator.services.mozilla.com/D157706

nsMathMLOperators::LookupOperators(s) methods are currently use in three
places:

(1) In nsMathMLmoFrame::ProcessTextData(), where we need to check the
    flags for each form of the operator and take the bitwise-or of all
    of them, ignoring lspace/rspace.

(2) In nsMathMLOperators::GetStretchyDirection::ProcessTextData(), where
    we need to check the direction for each form of the operator (in any
    order) and return the first found, ignoring lspace/rspace.

(3) In nsMathMLmoFrame::ProcessOperatorData, where need to check the
    specified form, and try fallback forms in the order prefix, postfix,
    infix. When an entry is found, the code also clears the form bits of
    mFlags and bitwise-or the found flags.

This commit modifies nsMathMLOperators::LookupOperator to only check
one form at once and can be used to easily implement (1) and (2). This
removes the need for nsMathMLOperators::LookupOperators.

A new method nsMathMLOperators::LookupOperatorWithFallback is introduced
to preserve the fallback prefix/postfix/infix check that is needed for
(3). Undocumented bitwise logic is moved out of that method.

Differential Revision: https://phabricator.services.mozilla.com/D157705

Bug 1777060 - disable test_caret_move_in_vertical_content.html on android debug r=intermittent-reviewers,MasterWayZ DONTBUILD

Differential Revision: https://phabricator.services.mozilla.com/D157917

Bug 1790644 - Ensure default search engine settings are correctly preserved during and after experiments. r=daleharvey

Differential Revision: https://phabricator.services.mozilla.com/D157850

Bug 1789866 - Update the directory mapping to reflect that wpt performance-related tests belong to Core::DOM: Performance r=sefeng

Differential Revision: https://phabricator.services.mozilla.com/D156862

Differential Revision: https://phabricator.services.mozilla.com/D157559