It's a more useful number since we also report the number of existing and rasterized picture cache tiles.
Also bump the expected number of alpha passes up to 2 since it is rather common.
Differential Revision: https://phabricator.services.mozilla.com/D52134
--HG--
extra : moz-landing-system : lando
During high contrast mode, alpha is used by SwapChain. In this case, IDXGISwapChain1::Present1() shows nothing with compositor window. To address the problem, we disable the Present1() usage when alpha is used.
Differential Revision: https://phabricator.services.mozilla.com/D52511
--HG--
extra : moz-landing-system : lando
Instead of creating a picture caching slice for any content that
is fixed position, also check if the clip(s) for the cluster are
fixed position or anchored to the scroll root.
This prevents WR creating slices for parallax style effects. There's
not much point in doing this anyway, since those slices will invalidate
due to the spatial node of the clip changing during scrolling. This
also allows subpixel AA to be enabled in more situations.
Differential Revision: https://phabricator.services.mozilla.com/D52621
--HG--
extra : moz-landing-system : lando
These settings are now supplied during layer creation and never change.
Consumers must now create new NativeLayer objects if they want to change size or toggle opaqueness.
This aligns the NativeLayer API with DirectComposition's capabilities. It also simplifies swap chain
management.
Differential Revision: https://phabricator.services.mozilla.com/D51757
--HG--
extra : moz-landing-system : lando
These helpers will be used by the image decoders in the next part of
this series.
Differential Revision: https://phabricator.services.mozilla.com/D52007
--HG--
extra : moz-landing-system : lando
This reduces the amount of invalidation on some pages very significantly.
It also fixes a number of cases where picture caching "fails", resulting
in everything invalidating every frame.
Differential Revision: https://phabricator.services.mozilla.com/D52275
--HG--
extra : moz-landing-system : lando
Add a first pass at invalidation debugging infrastructure. Also
tidy up the locations that invalidate into a common method, that
sets the invalidation reason.
Differential Revision: https://phabricator.services.mozilla.com/D52128
--HG--
extra : moz-landing-system : lando
It's possible to have a fixed offset-path together with other animating
css transform properties or offset-* properties, so we have to update
this assertion.
Differential Revision: https://phabricator.services.mozilla.com/D52296
--HG--
extra : moz-landing-system : lando
These helpers will be used by the image decoders in the next part of
this series.
Differential Revision: https://phabricator.services.mozilla.com/D52007
--HG--
extra : moz-landing-system : lando
Removes NofityForUse() functions for simplicity.
Ensure that RenderTextureHost::PrepareForUse() is called before RenderTextureHost:: Lock(). When a task of calling RenderTextureHost::PrepareForUse() is simply posted to render thread, there is a case that RenderTextureHost:: Lock() is called before PrepareForUse() .
Differential Revision: https://phabricator.services.mozilla.com/D51974
--HG--
extra : moz-landing-system : lando
This avoids calling GetTextureForwarder during shutdown which may return a null pointer.
Differential Revision: https://phabricator.services.mozilla.com/D51615
--HG--
extra : moz-landing-system : lando
This also moves the 'mach' docs from /python/mach to /mach. The reason being
that 'mach' doesn't really have anything to do with Python other than its
implemented in it.
Differential Revision: https://phabricator.services.mozilla.com/D52253
--HG--
extra : moz-landing-system : lando
The `setCompositionRecording` API on nsIDOMWindowUtils has been broken up into
two new APIs:
* `startCompositionRecording()`, which starts the composition recorder; and
* `stopCompositionRecording(bool writeToDisk)` which stops the composition
recorder and either returns a Promise that resolves to the collected frames
or returns a Promise that resolves when the frames have been written to disk.
The collected frames are serialized over IPC as part of a Shmem as to not
approach the IPC data transfer limit.
Differential Revision: https://phabricator.services.mozilla.com/D47818
--HG--
extra : moz-landing-system : lando
The composition recorder can now either write frames to disk as PNGs or return
the frames as an array of data URIs. This will allow us to send the collected
frames across IPC and hand them over to JS in a later patch.
Differential Revision: https://phabricator.services.mozilla.com/D47815
--HG--
extra : moz-landing-system : lando
`windowUtils.setCompositionRecording()` now returns a promise that is resolved
when the composition recorder is enabled (if given `true`) or when frames are
written to disk (if given `false`). To accomplish this, the
`WebRenderCompositionRecorder` now returns a `MozPromise` when writing frames
to disk begins that is resolved when that process finishes.
Differential Revision: https://phabricator.services.mozilla.com/D47300
--HG--
extra : moz-landing-system : lando