I'm guessing that it got moved into the wrong file for the Quantum DOM
split into CCJSContext and CCJSRuntime. The only use is in the latter
so it makes sense to have it there.

Original Revision: https://phabricator.services.mozilla.com/D192638

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

Bug 1861742 - Part 2: Traverse ReadableByteStreamQueueEntry and PullIntoDescriptor r=smaug, a=RyanVM

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

Bug 1861742 - Part 1: Move ReadableByteStreamQueueEntry and PullIntoDescriptor to cpp r=smaug, a=RyanVM

They are not used by other files.

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

Bug 1858570 - Fix relative URL path starting with multiple slashes r=necko-reviewers,kershaw a=RyanVM

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

The "righter" way to do this is adding a bunch of min-height: 0 to the
grid, the dialog, the content box, etc. But this is more similar to what
other dialogs do.

Original Revision: https://phabricator.services.mozilla.com/D180890

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

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

This is what we did before the fix for bug 1779578.
Failure to do this meant that RemoteAccessible::IsLink() returned false even for a child of a HyperText Accessible, which meant the ATK object was created without the HyperLink interface.
This change requires that we move the handling of pending OOP child docs, since we can't add a child document until ProxyCreated has been called on the OuterDoc.

Original Revision: https://phabricator.services.mozilla.com/D186423

Depends on D192440

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

Bug 1779578 part 2: Split serialization of a11y subtrees across multiple IPDL calls if we are likely to exceed the IPDL maximum message size. (ESR)  a=RyanVM

In the content process, we simply split into multiple calls when the number of Accessibles exceeds our maximum.
The maximum is calculated to allow for every Accessible to consume 2 KB in the IPDL message.
Currently, this means we split every 131072 Accessibles.
Of course, we could still exceed this IPDL message size if one or more  Accessibles consumed a lot more than this; e.g. many labels longer than 2 KB.
However, this seems unlikely in the real world.
If this turns out to be a problem, we'll need to count the actual size of the serialized data for each Accessible.
For example, we could use AccAttributes::SizeOfExcludingThis, though that isn't exactly the serialized size.
I worry though that such data structure traversal could get expensive at scale.

In the parent process, we defer attaching the root of the new subtree to its parent until the final call.
This is achieved by saving the root during the first call and using that to attach and fire events in the final call.

Original Revision: https://phabricator.services.mozilla.com/D184367

Depends on D192439

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

Bug 1779578 part 1: When serializing a11y subtrees, include parent id and index in parent for each Accessible. (ESR)  a=RyanVM

When we serialize a subtree, we put it into a flat list.
Previously, we included the child count for each Accessible so that we knew how many Accessibels to consume as children when de-serializing.
We also de-serialized recursively.
This made it very difficult to split serialization across IPDL calls, since we would always end up splitting in the middle of some Accessible's children.
Instead, we now no longer include the child count, but we do include the parent id and the index of the child in that parent.
This means that each Accessible can be de-serialized independently and iteratively, making it possible to split wherever we need to.
RemoteAccessible creation has also been separated from attachment of the child to its parent, since we will need this when splitting.

Original Revision: https://phabricator.services.mozilla.com/D184366

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

Bug 1854090 - Omit psnames of fonts with family-name *.tmp from src:local() lookups on Windows. r=jwatt, a=dsmith

This is a sad hack, but aims to work around the issue that some
PDF-related software (Acrobat is suspected but not currently confirmed)
is potentially polluting the global font collection with re-encoded
subsets of standard fonts like Arial, but does not munge the psname;
these can then be returned by src:local(...) lookups, which results in
garbled or missing text.

In principle, if such fonts are "installed", Firefox is not wrong to use
them; it's just a badly-configured system. But given that it seems to be
caused by some PDF-handling software, without the user's knowledge, it
seems worth trying to avoid the problem. Simply skipping the psname of
any font with family-name *.tmp is highly unlikely to adversely affect
any real-world content.

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

Bug 1860767 - Replace MOZ_ReportCrash call for AutoEnterOOMUnsafeRegion with fprintf. r=jonco, a=dsmith

According to bug 1859737, there are some issues with the stack dumping code on Windows
and the goal is to stop defining `MOZ_ReportCrash` in non-debug builds.
For `AutoEnterOOMUnsafeRegion` it seems simplest to do our own printf.

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

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

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

Bug 1818757 - Increase network triggering timeout in test_race_cache_with_network.js r=necko-reviewers,jesup, a=test-only

100ms is probably too little and in some cases the cache may not be
fast enough to fulfil the request - which is what the test is expecting.

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

This is a speculative crash fix; I don't know how to reproduce this problem.
A non-XUL (HTML, SVG, etc.) table cell should always have a CachedTableAccessible ancestor.
Apparently, this sometimes isn't the case.
It seems there can be a table ancestor which is not a CachedTableAccessible, which could only be a XULListboxAccessible or XULTreeGridAccessible.
In this case, CachedTableCellAccessible::GetFrom would previously try to cast this TableAccessible to a CachedTableAccessible and breakage would ensue.
I don't know how this can happen, but we protect against this now by returning early if a XUL table is found, since a XUL table can never be a CachedTableAccessible.
In contrast, all non-XUL tables are always CachedTableAccessibles.

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

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

Setting the "selectedIndex" attribute doesn't trigger all the relevant
side effects. It's also simpler.

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

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

Depends on D191597

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

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

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

This allows for disabling WebGL's use of GL_KHR_no_error, rather than the default of enabled.

Use snake_case so that searching for KHR_no_error finds this more
easily.

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

In the case where the LayerTreeState for the input content LayersID
was found, but its mParent was null for some reason, the function
was incorrectly returning the content LayerTreeState.

Instead, in such a case, where the root LayerTreeState cannot be
looked up, the function should return null.

Original Revision: https://phabricator.services.mozilla.com/D190143

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

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

Bug 1859030 - Exit early in WorkerManagerCreatedRunnable::Run if the actor cannot send. r=dom-worker-reviewers,asuth, a=dsmith

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

Bug 1658432: Don't remove wrapping CALayer from its superview outside of Commit. r=mac-reviewers,mstange, a=dsmith

This change lets NativeLayerRootCA::Representation::Commit be the only
point where sublayers are added and removed from the root CALayer.

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

Bug 1855345 - Make `AutoCopyListener` ignore any selection changes caused by Selection API r=karlt,smaug, a=dsmith

Even though there is a reasonable usabe like bug 1567160, we should
ensure that `AutoCopyListener` never update clipboard when the selection
change is caused by a Selection API call.

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

This patch doesn't change behavior; it just removes some redundant checks.

(Note that the tight-scoping around nsAutoMicroTask/ReduceAnimations is
important for the RAII object to be torn down at the intended time; but it
doesn't need its own if-check.)


Original Revision: https://phabricator.services.mozilla.com/D191911

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

This patch doesn't change behavior.

This is a bit gross, but it helps us make better use of the backtrace to figure
out what's going on in a given crash report.

Original Revision: https://phabricator.services.mozilla.com/D191909

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

Bug 1861259 part 1: Refactor out a helper function for loop body in nsRefreshDriver::Tick.  a=diannaS

This doesn't affect behavior; it's just a pure refactoring, moving code from
being inline to being in a helper function.

Original Revision: https://phabricator.services.mozilla.com/D191908

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

These telemetry probes have long since expired, so remove them. This
avoids taking unnecessary timestamps in these functions, which we have
seen can be expensive on certain devices.

Original Revision: https://phabricator.services.mozilla.com/D185007

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

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

Bug 1860531 - Add new queryParamNames option to search-telemetry-v2 schema for specifying multiple query parameter names. r=search-reviewers,jteow a=RyanVM

This is a new option that allows specifying multiple query parameter names, so that we can support
some search engines on mobile, where they use a different parameter name to desktop.

A future changeset will make 'queryParamNames' a required parameter.

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

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