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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

Historically there were kludges in how we chose to snap layers and
transforms, nominally for performance reasons (see bug 602200 comment
36). WebRender appears to render what was considered at the time the
ideal outcome, which also makes the most sense as a content author.
Given we are otherwise lacking a reason to continue with the old
behaviour, this patch adds a new test case to confirm WebRender snaps in
the ideal fashion, and non-WebRender does not.

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

--HG--
extra : moz-landing-system : lando

Bug 1601219 - Use the right PageStyleFront instance when querying computed styles from the color picker; r=rcaliman

It looks like we left out some places in the inspector when we made it fission-compatible.
The color-picker, in particular, needs access to the selected node's computed style for its
color contrast logic.
We used to access this on the top-level target PageStyleFront. We just need to change this so
it uses the one contextual to the selected node.

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

--HG--
extra : moz-landing-system : lando

Bug 1593674 - remove marionette VideoStream  YouTube test as it's duplicated in raptor r=tarek,marionette-reviewers,whimboo

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

--HG--
extra : moz-landing-system : lando

Bug 1600715 - Match the order of the extraParams for search engines to the existing lists. r=mikedeboer

We might as well do this for now to keep the tests passing when modern config is turned on. It doesn't actually matter what order these particular parameters are listed in.

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

--HG--
extra : moz-landing-system : lando

Bug 1600715 - Change the searchUrlParams in the modern config to be an ordered array of objects. r=mikedeboer

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

--HG--
extra : moz-landing-system : lando

Bug 1444426 - Remove the 'Automatically update search engines' option from preferences as it is confusing and doesn't fully apply now. r=mikedeboer,fluent-reviewers

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

--HG--
extra : moz-landing-system : lando

This fixes quite a bit of historical baggage, and also goes
into a bit more details of what the l10n repacks actually do.

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

--HG--
extra : moz-landing-system : lando

Bug 1601006 - Fix download location of fenix performancetest apk in CI for raptor-browsertime r=stephendonner

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

Now all loops use either JSOP_IFNE (do-while) or JSOP_GOTO (other loops).

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

--HG--
extra : moz-landing-system : lando

For now we still need the source note itself to determine the
stackPhiCount in IonBuilder. Hopefully we can fix that later.

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

--HG--
extra : moz-landing-system : lando

This allows removing the source note offset in the next patch.

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

--HG--
extra : moz-landing-system : lando

It's now always called from IonBuilder::jsop_loophead.

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

--HG--
extra : moz-landing-system : lando

Mechanical rename/merge for the most part.

When restarting a loop in IonBuilder, we skip the JSOP_LOOPHEAD so we
now re-add the interrupt check (this used to be done by JSOP_LOOPENTRY)
explicitly by calling emitLoopHeadInstructions.

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

--HG--
extra : moz-landing-system : lando

This is necessary for the next patch: it will merge JSOP_LOOPHEAD
and JSOP_LOOPENTRY but that means there can be multiple callVMs for
that op and this confuses DebugModeOSR (interrupts can trigger debugger
recompilation).

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

In visitTestBackedge we can just get the backedge target from the
bytecode instruction.

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

--HG--
extra : moz-landing-system : lando

All loops now use State::DoWhileLike so we can don't need to keep track of the
state anymore and can remove some more dead code.

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

--HG--
extra : moz-landing-system : lando

All loops now have the same structure. A later patch in the stack
will remove this class.

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

--HG--
extra : moz-landing-system : lando

This changes all loops to have the following bytecode structure:
```
JSOP_LOOPHEAD
JSOP_LOOPENTRY
...condition/body...
JSOP_GOTO/JSOP_IFEQ/JSOP_IFNE
```

This simplifies IonBuilder a lot because it can use the do-while code path
for all loops. For-in loops are also a bit simpler now because they no longer
need to have the next enumerated value on the stack across the backedge.

Later patches in the stack wil fold JSOP_LOOPENTRY into JSOP_LOOPHEAD,
simplify the source notes more and remove more code from IonBuilder.

I verified stepping/breakpoints for the different loop types works in the
debugger the same way as before this patch.

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

--HG--
extra : moz-landing-system : lando

The old code used the beforeLoopEntry bytecode pc, but this wasn't always
the correct pc and fixing that is a bit annoying (IonBuilder would have to
keep track of the last pc just for this).

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

The size of the visible region, for either a painted layer or a webrender blob
image, is calculated from the building rects of the contained display items, in
local-space. This should be restricted to the display port, to prevent the
visible regions growing too large leading to excessive memory usage.

For items within large scale transforms, the local-space visible region should
be very small. However, as we do not allow fractional sizes, the size of the
visible region will be rounded up to at least 1. This means that when we convert
the region back to screen-space, we are multiplying the extremely large scale by
at least one, rather than by a much smaller fraction. This can result in
incredibly large visible regions, and was causing OOM crashes.

To avoid this, we clamp the maximum chosen scale for these layers/blob images to
32k. Layers affected by this problem should have a visible region with
dimensions of 1 or 2, so this limits the resulting screen-space size for
those to an acceptable value. Layers with visible regions sized greater than
that should not have scales anywhere near this large, so will not be affected.

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

--HG--
extra : moz-landing-system : lando

In bug 15311428 we made it so that when a spatial node is being pinch-zoomed we
use a local raster-space to avoid rerasterizing glyphs for every slight change
in zoom level. This makes it so that we also apply the same trick when
being asynchronously zoomed by a double-tap gesture.

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

--HG--
extra : amend_source : ed5cc9dae872e18c012f4483e1cc94676dd2580b

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

--HG--
extra : moz-landing-system : lando

Backed out changeset 26f4282834a3 (bug 1601197) for causing condprof failures in condprof/tests/test_client.py CLOSED TREE

--HG--
extra : rebase_source : 6280869a7d32fa412c0ee658290258a619cf86e0

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

Bug 1601197 - Make sure the condprofclient picks mozilla-central artifacts by default r=stephendonner

The client will pick condprofs from mozilla-central by default

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando

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

--HG--
extra : moz-landing-system : lando