Bug 1613790 - Implement module to measure performance of TRRs and send telemetry. r=johannh,dragana,valentin

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

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

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

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

Since the thread actor caches the object actors
it creates, if an object had multiple properties
referencing the same object, we would create
multiple fronts for the same object actor, which
would confuse protocol.js.
The fix consist in checking if a front already exists
before creating a new one.
A test is added for the debugger to ensure this
works as expected and we don't regress.

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

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

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

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

backports.lzma couldn't cleanly be installed because we were now using Python3.8 but hadn't specified that in the Pipfile. Also took the opportunity to remove the pip version restriction which is no longer needed.

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

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

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

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

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

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

Depends on D63952

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

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

Backed out changeset 49e61b566da1 (bug 1596513)
Backed out changeset 889cee140af8 (bug 1596513)

Introduced in:
https://gitlab.gnome.org/GNOME/glib/commit/8aeca4fa647bfd0f35c4a86b1e6ca6e955519ca5

Shipping in glib 2.63.5 (available in Debian experimental)

Thanks to @padenot for the suggestion!

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

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

getStackPointer is non-static on arm64 so accesses must be via member access: masm.getStackPointer.
But it is static on other platforms, so the member access ticks off the static checkers.
Just make it non-static everywhere; it'll get inlined and boil away in any case.

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

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

Since the thread actor caches the object actors
it creates, if an object had multiple properties
referencing the same object, we would create
multiple fronts for the same object actor, which
would confuse protocol.js.
The fix consist in checking if a front already exists
before creating a new one.
A test is added for the debugger to ensure this
works as expected and we don't regress.

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

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

WebRender expects drop shadow dx/dy to be in user space, which is a floating point value.
Before this, a dx/dy such as (0.2, 0.2) was truncated to (0, 0) resulting in no offset of the shadow.

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

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

Bug 1596513: Part 1: Take scale factors into account when rendering drop shadows in WebRender r=gfx-reviewers,kvark

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

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

Bug 1616254 - MatchScope should check same-origin using ScopeToPrincipal helper r=dom-workers-and-storage-reviewers,asuth

Fixes an issue where directly converting a string to principal causes the
string to fail to be parsed due to "^" being interpreted as the start of
origin attributes (and the rest of the string isn't able to be parsed as
origin attributes).

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

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

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

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

Bug 1616539 - Make `TextEditor::OnDrop()` compare newly focused element with active editing host r=m_kato

Currently, it checks whether proper element gets focus as expected with
`nsFocusManager::GetFocusedElement()`, but it returns globally focused element.
I.e., it may return different document's element or `nullptr` if application
itself is inactive.

The purpose of the focus check is, `HTMLEditor` can modify contents only in
active editing host.  Therefore, comparing with
`HTMLEditor::GetActiveEditingHost()` is better and simpler for here.

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

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

this change adds an ability to create WebGPU textures, views, and samplers

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

--HG--
extra : source : 8f51a5fac21cb52e2ddb647f0b99a9bfccb41f6a

Backed out changeset 9c3d85e9b9fe (bug 1562412)
Backed out changeset e39e5d6a77a8 (bug 1562412)
Backed out changeset aa62038d5d76 (bug 1562412)
Backed out changeset 2143a26de372 (bug 1562412)
Backed out changeset 5b7ca7cf6649 (bug 1562412)
Backed out changeset 7870fa417606 (bug 1562412)
Backed out changeset bf7896916b91 (bug 1562412)
Backed out changeset cd6f0176af52 (bug 1562412)
Backed out changeset af8ccde58367 (bug 1562412)
Backed out changeset 9be172fa19e1 (bug 1562412)
Backed out changeset 9ccdef3b8c9d (bug 1562412)
Backed out changeset 0fc1845ea46c (bug 1562412)
Backed out changeset 861e4a4a13aa (bug 1562412)
Backed out changeset 32f31a6daaa8 (bug 1562412)
Backed out changeset b51ce1cea46d (bug 1562412)
Backed out changeset b8ddcf8368c5 (bug 1562412)
Backed out changeset 19ac1668f0db (bug 1562412)

Backed out changeset 7910393bf14a (bug 1589248) for Newtab failures on karma | activity-stream:DiscoveryStreamFeed:#loadLayout. CLOSED TREE

Bug 1616422 - Part 2: Update display item cache state after call to CreateWebRenderCommands() r=jrmuizel

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

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

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

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

Bug 1530857 - Clear isRunningCompositor flag when the corresponding display item for background-color animations is discarded. r=boris

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

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

Based on crash stats the crash is null+offset, and I think the issue can happen during closing down
BrowserChild if there is a pending RecvSizeModeChanged message.
The crash has been there for ages, I think since bug 1104916

Note, BrowserChild::RecvUpdateDimensions does have a null check for the document.

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

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

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

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

Depends on D61348

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

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

Depends on D61347

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

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

Depends on D61346

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

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

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

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

This removes `nsAutoPtr` usage from ipc/. security/ failed to build due to missing includes so I fixed that as well. IDB was using `ThreadLocal` from ipc which had a member changed to a `UniquePtr` so needed to be updated as well. localstorage was missing some includes.

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

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

This adds a `getter_Transfers` implementation for `UniquePtr` suitable as a drop-in replacement for the `nsAutoPtr` variant.

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

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

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

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

CLOSED TREE

Backed out changeset 3d44ebc7aed0 (bug 1616422)
Backed out changeset d17dbf82cdd0 (bug 1616422)

Add a test to cover app approval for EME. The test is not currently targeted at
android despite the feature being made for GeckoView. This is because we do not
have clearkey support on Android, and cannot guarantee Widevine support. If we
have broad Widevine support on Android we could rework the test to use that when
on Android.

For now having some test coverage on clearkey platforms seems better than having
no test coverage.

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

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

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

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

Bug 1587522 - Surface events from MediaKeySystemAccessManager to let the app wrapping gecko allow or deny EME. r=alwu

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

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

This class will be used to surface permission requests to GeckoView.

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

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

Bug 1587522 - Add media.eme.require-app-approval pref to control if EME needs app permission. r=alwu

Add a pref that we can gate the EME app approval behaviour behind. If the pref
is true we'll ask app for approval via a permission request. The intended use
for this is to allow GeckoView to seek explicit approval from the embedding app.

Having this pref is also useful for testing outside of GeckoView as it allows
runtime configuration of the permission check.

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

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