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

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

Depends on D43366

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

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

Depends on D43570

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

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

Depends on D43364

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

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

FirstStartup provides an optional mechanism to run synchronous services
before the UI appears. This is intended to be called as a post-install
action from an installer, such as the Windows Stub Installer, to allow
for downloading critical data and performance tuning before the first
run of a new Firefox install.

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

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

The tile size is configurable with the prefs layers.compositing-tiles.width/height.

On macOS, whenever a CALayer is touched, the window server will recomposite the
entire layer to the screen. There is no API to mark parts of a layer as damaged.
So if we want the window server to only redraw a small part of the screen, we
need to only touch small layers. This patch achieves that using tiles; whenever
the compositor needs to redraw an area, all tiles that overlap this area will
be drawn to their layers and the window server will recomposite those layers.

On Intel GPUs, compositing in tiles should also help reduce GPU times if there
are multiple layers of overdraw: The overdraw will have better cache locality.
However, the magnitude of this effect is not known and requires further research.

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

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

Bug 1574586 - Create separate NativeLayer objects for opaque and transparent parts of the window, and do one composite each to draw their contents. r=mattwoodrow

This means that when something changes in an opaque layer, the window server
only needs to copy the opaque layer to the screen and can avoid recomputing any
window backgrounds for transparent parts of the window. This can save power,
especially when transparent parts of the window use the macOS vibrancy effect,
which requires the window server to compute a blur and to composite windows
behind our window.

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

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

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

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

This change surfaces errors faster, and ensures that we don't silently
end up with empty crashreporter symbols if `dump_syms` can't run for
some reason.

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

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

Just some minor prefixing needs to be done to enable this.

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

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

Depends on D43781

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

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

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

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

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

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

Backed out changeset 204d32b36d7e (bug 1575240) for frequently failing devtools at  devtools/client/inspector/test/browser_inspector_menu-06-other.js

Bug 1577752 - Use padding-block and padding-inline for the urlbar's one-off search button adjustments. r=harry

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

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

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

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

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

--HG--
extra : source : cd8cfdc6b5b3d0ce775afda2bb3c443451baa20f
extra : histedit_source : c048c74d4a7f8cdf3d245c1ad0e4a875c7e0b1a7

Bug 1577362 - Disable browser_allowListSeparationInPrivateAndNormalWindows.js on fission. r=intermittent-reviewers,jmaher

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

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

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

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

I would like to log `IMEState` and `InputContextAction`in widget. But this
utilities are in `IMEStateManager`, so I would like to move it to widget
by using `mozilla/ToString.h`.

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

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

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

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

Bug 1577053 part 3: Add lang="ja" to text-emphasis reftest files that weren't regenerated by the scripts in the support subfolder. r=jfkthame

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

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

This patch was generated by running each of the scripts in the folder
layout/reftests/w3c-css/submitted/text-decor-3/support/

(This patch also includes a manual edit to reftest.list, to annotate some Win7
fuzziness that was caused by the new choice of font for a set of tests here.)

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

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

Bug 1577053 part 1: Update generate-text-emphasis-* test creation scripts to add lang="ja". r=jfkthame

Also, adjust the scripts to leave behind a note in each generated HTML file, to
tell the reader that the file is auto-generated.

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

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

--HG--
extra : amend_source : 3fcae6bae609b58437fbc1e981dc00b03a3e3432

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

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

This change breaks the draw-fps overlay when using native layers. I'll try to
fix that in a new bug soon.

The do { } while(0) loop looks a bit odd, but it'll get replaced with a proper
loop in bug 1574586.

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

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

This change groups the work that has to be done per compositing tile.

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

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

Bug 15747452 - Maintain a full window render target when rendering to native layers with CompositorOGL. r=mattwoodrow

This makes profiler screenshots and frame recording work again, when native
layers are used. The copying is a bit unfortunate. Maybe we can combine this
copy with the first downscaling step in the future. Or for frame recording,
which doesn't use downscaling, we could readback the layers individually and
reassemble them in CPU memory. But both of those solutions are more complex
than this.

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

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

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

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

Bug 15747452 - Move ShouldRecordFrames() from BasicCompositor to Compositor because CompositorOGL will need it. r=mattwoodrow

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

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

This is so that we can invalidate all layers when screenshot profiling has
started, and not just the first layer.

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

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

This will let us render into multiple layers within one compositor frame.

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

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

This removes any *TargetContext methods from the Compositor interface and moves
 mTarget tracking into the compositor implementations.

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

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

In the end we want to have BeginFrameForWindow, BeginFrameForTarget, and
BeginFrameForNativeLayers, the latter with multiple Begin/EndRenderingToNativeLayer
pairs nested inside.

This is the first step.

CompositorOGL and CompositorD3D11 keep their internal BeginFrame method but make
it private.

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

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

The call to TransformAndClipBounds already clips destRect to renderBounds.
However, if the resulting rect was empty, the Inflate call would make it
non-empty again. And now the decision whether we would cull would depend on the
rect's position: Sometimes TransformAndClipBounds would place the empty rect at
a position along an edge of renderBounds, and then the inflated-from-nothingness
2x2 rect would overlap renderBounds and we wouldn't cull.

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

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