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

It was generated by mixing every commit with "ignore-this-changeset" and
everything listed in .hg-annotate-ignore-revs, in topologic order.

The format was changed to:

  ```
  # hg-sha1 - author - subject
  cinnabar-sha1 # cinnabar
  gecko-dev-sha1 # gecko-dev
  ```

The comment line corresponds to entries in .hg-annotate-ignore-revs (or
what they would look like for commits with "ignore-this-changeset").

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

Bug 1633969 - Adjust messages in .hg-annotate-ignore-revs to match what is actually in the changesets. r=sylvestre

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

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

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

Bug 1633969 - Add changesets that appear in .git-blame-ignore-revs but aren't already marked as ignored for mercurial. r=sylvestre

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

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

Per its definition in v-c-t, hg smart-annotate skips them in addition to
the contents of the .hg-annotate-ignore-revs file, so they don't need to
appear in the file.

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

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

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

CLOSED TREE

Backed out changeset d339ce87c2ef (bug 1622384)
Backed out changeset 13101fc544bc (bug 1622384)
Backed out changeset aad4412b43e2 (bug 1622384)
Backed out changeset eba5d05e59b2 (bug 1622384)

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

Bug 1622384: Fix this test to not expect onn, and add a slightly different test that should expect onn at the very end. r=jib

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

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

JSEP transceivers were previously held in a vector, in the order that they were
created. However, these could be removed, which meant that the indexing was not
stable. Under most circumstances this did not matter, however there was a
wrinkle with implicit rollback in repeated sRD. Re-applying a remote offer that
had created a transceiver would destroy that transceiver, and create a new one
to replace it. However, JS was not informed, because to PeerConnectionImpl it
looked like nothing had changed. Now, transceivers are indexed in a stable way,
which allows this bug to be fixed, and makes things a little less confusing.

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

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

Backed out changeset d91e35044576 (bug 1630066) for failures on test_ext_sendmessage_reply2.html. CLOSED TREE

Backed out changeset 2a3f592412a2 (bug 1624954)
Backed out changeset 74085e028726 (bug 1624954)

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

Bug 1624954: Send state-change event when aria-haspopup value is changed to allow for caching. r=eeejay

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

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

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

When the browser process starts a sandbox process, we copy the executable's IAT
for ntdll.dll into the new process to prevent DLL injection via IAT tampering as
the launcher process does.  However, if IAT has been modified by a module injected
via `SetWindowHookEx`, the browser process cannot copy IAT because a modified IAT
is invalid in a different process, failing to start any sandbox processes.

The proposed fix is to cache IAT before COM initialization which may load
modules via `SetWindowHookEx` for the first time in the process.

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

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

reduce frequency of mingw* builds.

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

The implementation of this was previously ignoring the aRegion
parameter, so was completely broken. This is only used by the
Win7 widget code. This may fix an issue with drawing of window
close buttons on Windows 7 with WebRender enabled.

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

Bug 1634203 - Replace Kinto client with RemoteSettings client in test_remote_settings_poll r=glasserc

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

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

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

We're setting the background but not the text color on the light theme,
which means that  per these two rules:

  https://searchfox.org/mozilla-central/rev/7fd1c1c34923ece7ad8c822bee062dd0491d64dc/toolkit/themes/shared/findBar.inc.css#63-64

You'll get:

  background-color: #fff;
  color: -moz-FieldText;

If you have a dark system theme (like Adwaita Dark on Linux) where
-moz-FieldText is white, then badness happens and you get white-on-white.

The color is just tab_background_text, which seems to work quite nicely
and is the same that the dark theme does for this field.

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

Bug 1633704 - [wpt-sync] Update web-platform-tests to 7d7a74e34d6d9853a3d457c6d5ef1cfc0c55fbb6, a=testonly

MANUAL PUSH: wpt sync bot

wpt-head: 7d7a74e34d6d9853a3d457c6d5ef1cfc0c55fbb6
wpt-type: landing

wpt-pr: 23250
wpt-type: metadata

Automatic update from web-platform-tests
LazyLoad: Fix feature-policy tests

This updates the lazyload attribute as 'loading' with values of auto,
eager and lazy for the feature policy tests.

TBR=hiroshige@chromium.org

Fixed: 1074608
Change-Id: If8ba1d09bce518ac36b70bd2a7b01687ffec87c1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2166638


Commit-Queue: rajendrant <rajendrant@chromium.org>
Reviewed-by: Scott Little <sclittle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#763010}

--

wpt-commits: ddad50b245ec811f4cbce8c84639122e9a7732a9
wpt-pr: 23250

wpt-pr: 23163
wpt-type: metadata

Automatic update from web-platform-tests
Move 2d.getImageData.* in canvas_api to wpt

Move 2d.getImageData.* from canvas_api to wpt.

Bug: 1071659

Change-Id: I444088c44eb6f93d4800175deef05f99bfc8e98c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159913


Commit-Queue: Yi Xu <yiyix@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#763137}

--

wpt-commits: 9d33bb0defdd1625a3af3fe066b1acfc80b23895
wpt-pr: 23163

wpt-pr: 23243
wpt-type: metadata

Automatic update from web-platform-tests
Don't serialize closed shadow roots with getInnerHTML()

This CL corrects the behavior of getInnerHTML() so that closed
shadow roots are not serialized. It also adds a test of the
getInnerHTML() function.

Bug: 1042130
Change-Id: Iac214b16799cee45bcd90be8f618cc5560eb1db4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2166383


Commit-Queue: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#763236}

--

wpt-commits: c88ed219c1a65af9f83844181b84111e9462f8b6
wpt-pr: 23243

Bug 1630955 [wpt PR 23060] - [css-speech] rename Integer.html to voice-family-integer.html, a=testonly

Automatic update from web-platform-tests
[css-speech] rename Integer.html to voice-family-integer.html (#23060)

Renamed because it's one of few tests with capitalized filenames.
--

wpt-commits: b5e6c40a2bd4c4ae8bd64dad3f3732c023f150b4
wpt-pr: 23060

Bug 1633578 [wpt PR 23279] - [FragmentItem] Prevent dangling LayoutObject ptrs in block fragmentation., a=testonly

Automatic update from web-platform-tests
[FragmentItem] Prevent dangling LayoutObject ptrs in block fragmentation.

NGInlineCursor doesn't work with block fragmentation, so we'd end up
with NGFragmentItem objects with dangling pointers to LayoutObject. To
fix this, perform a full walk through all fragment items in all
fragments, if it's likely that we're in block fragmentation.

CL:2152824 caused two tests to crash because of this, and it therefore
got reverted. Add another test now, which would also crash without the
aforementioned CL.

Bug: 1075517
Change-Id: I97e2fae63d89031ea258ba146898e7fcfe56bd45
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2165800


Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#763233}

--

wpt-commits: e9ed833d0c9483012493d839434137de7e7ba00d
wpt-pr: 23279

wpt-pr: 23272
wpt-type: metadata