Bug 1716024 p2: Flag all binaries apart from firefox, xpcshell and plugin-container as CET compatible. r=glandium

We will only run the processes in CET compatible modules only mode when not
using the JIT code. So marking xul.dll as compatible should be OK.

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

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

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

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

When we close popup window we also pause compositor as EGL surface is deleted and we can't paint into it.

Paused compositor leads to pending WebRender transactions at nsRefreshDriver which has a bit though limit here and when we hit it
nsRefreshDriver stops to issue rendering event for all windows.

To avoid that when a window is hidden and compositor paused also clear pending WebRender transactions.

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

Now that ProxyWrappers (RemoteAccessibleWrap and friends) are gone, IsProxy() can never be true, so checking it is pointless.

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

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

Previously, when the cache was disabled, we had a RemoteAccessibleWrap for every RemoteAccessible.
This is no longer necessary and now only serves as an extra level of indirection and memory waste.
We still keep the stub MsaaAccessible to hold the id sent up from content.

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

Bug 1715230 part 3: Change AccessibleWrap::DispatchTextChangeToHandler to a static method accepting an Accessible*. r=morgan

In a subsequent patch, we want to call it with a RemoteAccessible instead of a RemoteAccessibleWrap.
As an instance method of AccessibleWrap, this wouldn't be possible because AccessibleWrap is a subclass of LocalAccessible.
Strictly speaking, there's no good reason for this to be part of AccessibleWrap at all any more, but I'm not dealing with that here.

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

This was previously used to wrap the COM proxy for the document child of an OOP iframe in a content process.
It was returned by OuterDocAccessible::LocalChildAt*.
Instead, BrowserBridgeChild now directly holds the COM proxy and MsaaAccessible traversal methods have specific code paths to return that as appropriate.

Since we no longer need the Windows OuterDocAccessible traversal overrides for OOP iframes nor remote top level documents, they have been removed entirely.

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

It still can't handle being called on a RemoteAccessible because Bounds isn't unified yet.
However, this allows it to be called on a local OuterDoc (a XUL browser element) and return a remote document child.
Previously, this was handled by the RemoteAccessibleWrap returned from OuterDocAccessible::LocalChildAt, but that will go away in a subsequent patch.

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

When the document is hidden from view, silently drop position updates on the floor. This aligns, more or less, with Chrome and Safari.

The situation with "not fully active" is a bit more quirky, because non-fully active documents are generally hidden (e.g., `remove()`ing and iframe).

Regardless, I think this gives us the desired behavior and covers the main privacy case: background tabs should not receive position updates.

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

This was used when defining scroll layers and also backdrop-filter.

Removing it from the scroll layer API allows removal of the implicit
clip rect that a scroll node previously created (Gecko doesn't use
this). To maintain compatibility with wrench tests, add a flag that
allows a test to specify a clip rect should be created for the scroll
layer (we should remove this from wrench in future and port the tests
to create explicit clip rects as required).

The usage of backdrop-filter was the only remaining place this type
was used, so it's now ported to use the clip-chain API.

This simplifies the scroll layer API and removes an extra clip rect
from each scroll layer instance, as a small performance improvement.

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

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

Bug 1720784 - Support toolbar-field-highlight in searchbar and fix theme mismatch issue. r=desktop-theme-reviewers,dao

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

Bug 1720534 - Clean up styles in Bookmarks Menu Button menupopups on Windows 7 and 10. r=desktop-theme-reviewers,dao

This also gets rid of a dead CSS class (panel-subview-footer).

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

Backed out 109 changesets (bug 1720549, bug 1720367, bug 1719919, bug 1720475, bug 1720524, bug 1719860, bug 1719934, bug 1720205, bug 1719181, bug 1719566, bug 1720690, bug 1719407, bug 1719562, bug 1719857, bug 1720813, bug 1719524, bug 1720811, bug 1720290, bug 1720635, bug 1720398, bug 1718029, bug 1571689, bug 1718698, bug 1718787, bug 1719182, bug 1720233, bug 1720421, bug 1720679, bug 1719923, bug 1719749, bug 1720588, bug 1718355, bug 1715840, bug 1718813, bug 1720745, bug 1720377, bug 1719409, bug 1718958, bug 1720372, bug 1720536, bug 1720553, bug 1720212, bug 1720929, bug 1719593, bug 1719865, bug 1718089, bug 1719862, bug 1719861, bug 1720596, bug 1718990, bug 1720904, bug 1719365, bug 1720100, bug 1719633, bug 1717581, bug 1720066, bug 1719635, bug 1718919, bug 1719174, bug 1719574, bug 1720385, bug 1718903, bug 1720992, bug 1715623, bug 1720653, bug 1718778, bug 1719772, bug 1719139, bug 1713253, bug 1719591, bug 1718609, bug 1719737, bug 1719767, bug 1717224) for causing sm failures.

CLOSED TREE

Backed out changeset 818df272f6e0 (bug 1720992)
Backed out changeset 7eee71d2d713 (bug 1720929)
Backed out changeset 227147027c52 (bug 1720904)
Backed out changeset ae7a3774b40c (bug 1720811)
Backed out changeset 72c6189e2aeb (bug 1720811)
Backed out changeset 4f1ebe2a6faf (bug 1720745)
Backed out changeset b6444ae3b823 (bug 1720745)
Backed out changeset 836c9f7cb430 (bug 1720813)
Backed out changeset a163466c7f99 (bug 1720653)
Backed out changeset a00b068f8045 (bug 1720653)
Backed out changeset 2dbc94c383f5 (bug 1720635)
Backed out changeset 2a9223785db5 (bug 1720635)
Backed out changeset beeb3d2d01b5 (bug 1720524)
Backed out changeset 2649351328e7 (bug 1720367)
Backed out changeset 42672daedc4c (bug 1718813)
Backed out changeset ae2103204fa8 (bug 1718813)
Backed out changeset 6b5bf1848875 (bug 1720553)
Backed out changeset 9c0bad4c477b (bug 1720290)
Backed out changeset 4f55d470b85b (bug 1720679)
Backed out changeset 6739faefd456 (bug 1720690)
Backed out changeset 63b60717adb9 (bug 1715623)
Backed out changeset e935afa24e76 (bug 1720372)
Backed out changeset aab897b961ff (bug 1720372)
Backed out changeset 600ab0cd3261 (bug 1718029)
Backed out changeset 2f464b21b0d0 (bug 1718029)
Backed out changeset 058f8d6e10f8 (bug 1720596)
Backed out changeset 086b66b43308 (bug 1720596)
Backed out changeset b2e0691f58ba (bug 1720588)
Backed out changeset 0db8ae67cd6a (bug 1720588)
Backed out changeset 982d1ecd2d01 (bug 1719772)
Backed out changeset 68f8048a3ce9 (bug 1719772)
Backed out changeset 4514b19b1dca (bug 1720385)
Backed out changeset 2ead0f2f8937 (bug 1720549)
Backed out changeset d88fc7ab0f6d (bug 1720421)
Backed out changeset 2b37d58c1e56 (bug 1720421)
Backed out changeset 25a774933b68 (bug 1720536)
Backed out changeset 68b16b1363b8 (bug 1719857)
Backed out changeset 069d6fde2a47 (bug 1720475)
Backed out changeset ffcf1987800d (bug 1720475)
Backed out changeset 89552b4ca5a2 (bug 1571689)
Backed out changeset 44663bd22f76 (bug 1571689)
Backed out changeset 360547491fb2 (bug 1717224)
Backed out changeset 9b65a80d9087 (bug 1719635)
Backed out changeset 78b09de6fdfc (bug 1719635)
Backed out changeset 5761d24ca1e7 (bug 1720398)
Backed out changeset af713fd12372 (bug 1720398)
Backed out changeset 894b083c110a (bug 1719934)
Backed out changeset a95b4f61dabb (bug 1719934)
Backed out changeset 3ecf9f0828c3 (bug 1720233)
Backed out changeset 8339cb3e70c8 (bug 1720233)
Backed out changeset 1ef81c9e982b (bug 1720377)
Backed out changeset 27f24ae74e6e (bug 1720377)
Backed out changeset b17610925ef9 (bug 1718778)
Backed out changeset 296736f90547 (bug 1718778)
Backed out changeset b62cf1edb080 (bug 1719633)
Backed out changeset 30b44dbbce0e (bug 1719633)
Backed out changeset cfd3c830e7a5 (bug 1718958)
Backed out changeset b625898cc6e7 (bug 1718958)
Backed out changeset 4522bdcac0da (bug 1720212)
Backed out changeset 1acc17ac2081 (bug 1720212)
Backed out changeset b964aca36f72 (bug 1713253)
Backed out changeset 3bc58e6bfaca (bug 1719919)
Backed out changeset 2e6245af4590 (bug 1719919)
Backed out changeset fccd5cdd2e8a (bug 1718903)
Backed out changeset 287402377378 (bug 1718903)
Backed out changeset af8a7029fc6d (bug 1720205)
Backed out changeset 017c2bcbb73b (bug 1719566)
Backed out changeset 07c998f93a3c (bug 1719566)
Backed out changeset 03792f0f5028 (bug 1719591)
Backed out changeset eacd82ff57d5 (bug 1719923)
Backed out changeset 726b2d0be39a (bug 1719174)
Backed out changeset fd6fd400d1dc (bug 1720066)
Backed out changeset f3d95dc6fe87 (bug 1719861)
Backed out changeset 6f230d5aa437 (bug 1720100)
Backed out changeset 91d988318f98 (bug 1720100)
Backed out changeset bb8654e35c2c (bug 1719139)
Backed out changeset d4e6e7c531c0 (bug 1719139)
Backed out changeset d934a9812b19 (bug 1719860)
Backed out changeset 14e040ae2974 (bug 1719860)
Backed out changeset e173de5102ce (bug 1719862)
Backed out changeset 485d2c910efc (bug 1718787)
Backed out changeset dfc6044fad53 (bug 1718787)
Backed out changeset 86279398edc7 (bug 1719865)
Backed out changeset c4f0971aa4bd (bug 1719181)
Backed out changeset db4e3bd46846 (bug 1719737)
Backed out changeset 6b5d4b0e570f (bug 1719737)
Backed out changeset 542a401a0e0b (bug 1719767)
Backed out changeset 0df0148648c6 (bug 1719767)
Backed out changeset 55c3e8587cf4 (bug 1719749)
Backed out changeset 22bea1f4e4a4 (bug 1719574)
Backed out changeset 1b415637c7ab (bug 1718355)
Backed out changeset f3c12cfe47dd (bug 1719593)
Backed out changeset c0a26ed925f6 (bug 1719562)
Backed out changeset 66d418216d04 (bug 1718990)
Backed out changeset b4d7756e4c38 (bug 1719182)
Backed out changeset 67c42f7d0752 (bug 1719524)
Backed out changeset a62f32295a25 (bug 1718698)
Backed out changeset 3853df088fef (bug 1718698)
Backed out changeset b8c8b8384c16 (bug 1718609)
Backed out changeset 9d8151e6eb89 (bug 1718089)
Backed out changeset 6748bdc27dd0 (bug 1718089)
Backed out changeset f7c043fef187 (bug 1715840)
Backed out changeset af3d5f56749b (bug 1719409)
Backed out changeset fee9007fd3e1 (bug 1719407)
Backed out changeset d896b79fa57e (bug 1717581)
Backed out changeset 6fb272284cf5 (bug 1717581)
Backed out changeset 9bf8f8f13ff1 (bug 1719365)
Backed out changeset ed737b4579bd (bug 1719365)
Backed out changeset d1c491b1f6d0 (bug 1718919)

Bug 1720992 - [wpt-sync] Update web-platform-tests to 56bf98c5c076670e7ef0d60f973c7061ca13cd1f, a=testonly

MANUAL PUSH: wpt sync bot

wpt-head: 56bf98c5c076670e7ef0d60f973c7061ca13cd1f
wpt-type: landing

Automatic update from web-platform-tests
Fix flaky test layout-instability/input-timestamp.html

layout-instability/input-timestamp.html test is flaky because we are
waiting for 500ms to change the layout after a click event. The click
event should report a layout shift entry to PerformanceObserver with
hadRecentInput to be true, the layout shift of the div will report
another layout shift entry to PerformanceObserver with hadRecentInput to
be false. 500ms is the interval of the excluding input window, so if we
just set the timeout to be 500ms, the test is flaky, because the click
event may not executed right away. I change the time delay to be 600ms
to reduce the flakiness.

Bug: 1221422
Change-Id: Ib960d98fe7ac7d0806a7152052465e9188afb2a9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3032268


Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#902699}

--

wpt-commits: 56bf98c5c076670e7ef0d60f973c7061ca13cd1f
wpt-pr: 29693

Bug 1720904 [wpt PR 29691] - [COEPForSharedWorker] Do not block worker with incompatible COEP, a=testonly

Automatic update from web-platform-tests
[COEPForSharedWorker] Do not block worker with incompatible COEP

Bug: 1226550
Change-Id: Id037a95461ac7931b0c14d62f0e7a295db06dd9b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3035102


Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Commit-Queue: Yifan Luo <lyf@chromium.org>
Cr-Commit-Position: refs/heads/master@{#902490}

--

wpt-commits: fc1ec16e468f57fa819defcd565f50bf5039a399
wpt-pr: 29691

wpt-pr: 29683
wpt-type: metadata

Automatic update from web-platform-tests
[LayoutNG] More OOF writing mode fixes in multicol

1. Previously, we had used the writing mode of the CB when setting
up the NodeInfo in NGOutOfFlowLayoutPart. However, we want to use the
writing mode of the builder instead since the OOF will be laid out
inside the fragmentainer children of the builder rather than the CB
itself (in the case of fragmentation).

2. When creating the CB rect for inline CB's, the start offset that
was used was relative to the inline's containing block. However,
since the OOF is laid out inside the fragmentainers, we need to
convert the inline CB's rect to take the writing mode of the multicol
into account.

The added tests are similar to those added in CL:3025848, but they
apply block/inline insets rather than using the static position.
The tests added in CL:3025848 were moved to a common directory
as those added in this CL.

Bug: 1228746
Change-Id: I6073683137d3bf58eea8ce6f355321e75046fb50
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3032909


Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#902447}

--

wpt-commits: 6ec8995cb9ae8922ca539ff2c6737f48142f7d03
wpt-pr: 29683

wpt-pr: 29679
wpt-type: metadata

Bug 1720745 [wpt PR 29679] - Update navigator.ink.requestPresenter() to use a dictionary param, a=testonly

Automatic update from web-platform-tests
Update navigator.ink.requestPresenter() to use a dictionary param

requestPresenter took in two params, a String |type| and an Element
|presentationArea|. The goal of the |type| param was to enable
requestPresenter() to be easily extensible in the future for other types
of presenters.

However, in its current state, it is a no-op param. For this reason,
after some discussion ([1], [2], [3]) it has been decided that the API
should be updated to instead just use a dictionary param. This will
still be easily extensible in the future, but won't require a string
param until then.

[1]: https://github.com/WICG/ink-enhancement/issues/20
[2]: https://github.com/w3ctag/design-reviews/issues/473#issuecomment-876612377
[3]: https://groups.google.com/a/chromium.org/g/blink-dev/c/ZtqwKR_HIAE

Bug: 1052145
Change-Id: I9ef18a04ab150fff8c8f173bfa209e10d90781f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3027884


Reviewed-by: Daniel Libby <dlibby@microsoft.com>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Commit-Queue: Mario Bianucci <mabian@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#902434}

--

wpt-commits: 94a65991bc0a5e5300241d7e8b0c699484751e11
wpt-pr: 29679

Bug 1720813 [wpt PR 29685] - [LayoutNG] Consider OOF positioned nodes as IsManagedByLayoutNG., a=testonly

Automatic update from web-platform-tests
[LayoutNG] Consider OOF positioned nodes as IsManagedByLayoutNG.

positioned: fixed NG elements whose containing block was the LayoutView
had issues (the legacy kind) with scrollbars.

We can avoid these issues by letting IsManagedByLayoutNG return true
when OOF. These are basically "managed" by NG as they are laid out
via. the NGOutOfFlowLayoutPart.

The other callers of IsManagedByLayoutNG should also be fine with this
change.
1) https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/frame/local_frame_view.cc;l=1539?q=ismanagedbylayoutng&ss=chromium
   Should be fine, OOF doesn't need to be pre-laid-out.
2) https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/layout/depth_ordered_layout_object_list.cc;l=53?q=ismanagedbylayoutng&ss=chromium
   Should also be fine as OOF?

Bug: 1225548
Change-Id: I42c4551382553ea52edc5f2ada94ce74d570c6bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3033195


Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#902402}

--

wpt-commits: 43315228ce863f064e2702e22804ecd381e5da70
wpt-pr: 29685

wpt-pr: 29673
wpt-type: metadata

Automatic update from web-platform-tests
[Sanitizer API] Move tests to WPT suite.

Bug: 1184655
Change-Id: I8d1279df84633683b7c42e0d344ee6d5094aa64a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3026791


Reviewed-by: Yifan Luo <lyf@chromium.org>
Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#902400}

--

wpt-commits: dca960f6bdc3892ebd1c171e5c06e71c12c7b751
wpt-pr: 29673

wpt-pr: 29671
wpt-type: metadata

Automatic update from web-platform-tests
Rename scrollbar-gutter "mirror" to "both-edges"

For clarity, the "mirror" value of the scrollbar-gutter property has
been renamed to "both-edges". The functionality remains the same.

CSS WG: https://github.com/w3c/csswg-drafts/issues/6349

Bug: 710214
Change-Id: I65683037e083f2edee21451f54a9ef34374d0988
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3026774


Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Felipe Erias <felipeerias@igalia.com>
Cr-Commit-Position: refs/heads/master@{#902287}

--

wpt-commits: 43b8e825b9d0bd67f812c08618266e6501b6da6e
wpt-pr: 29671

Automatic update from web-platform-tests
[EyeDropper API] Update implementation to match explainer.

Explainer:
https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/EyeDropper/explainer.md

I2P: https://groups.google.com/a/chromium.org/g/blink-dev/c/cPTMI1i6d7I/

The explainer was updated to address the tag review:
- moved to a promise based design (EyeDropper.open() returns a
Promise<ColorSelectionResult>)
- renamed the selected color property to sRGBHex to make it clear that
the color is a string and it is in sRGB (this allows room for future
properties to be added)

For now a manual test has been added, more test coverage is going to be
added in follow-up CLs.

Bug: 897309
Change-Id: Ib3631b94ff43cd59ba1640f0c295e233f058383a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3027321


Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Ionel Popescu <iopopesc@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#902121}

--

wpt-commits: ca5841f2435a1042649c99cf736918ad88a71098
wpt-pr: 29661

Bug 1720367 [wpt PR 29650] - Refactored scroll timeline tests to defaults to progress based testing., a=testonly

Automatic update from web-platform-tests
Refactored scroll timeline tests to defaults to progress based testing.

Converted a few tests to be progress based and fixed a conversion bug in
animation.cc

Bug: 1216655
Change-Id: I0882800677a4af0863883d59970594ea27cfb582
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3025004


Commit-Queue: Jordan Taylor <jortaylo@microsoft.com>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#902091}

--

wpt-commits: c4241caddefcd03ccb77935f71f5d787740cfb75
wpt-pr: 29650

wpt-pr: 29548
wpt-type: metadata

Bug 1718813 [wpt PR 29548] - [LayoutNG] Relative offset for OOFs with inline CBs in a multicol, a=testonly

Automatic update from web-platform-tests
[LayoutNG] Relative offset for OOFs with inline CBs in a multicol

Relative offsets should be applied after fragmentation. Since we perform
layout for OOFs once they reach the fragmentation context root (if
applicable), we fail to apply any relative offsets at the correct time
in the case of inline containing blocks. See CL:2851595 for how this
was handled for the non-inline case.

The changes required to accomplish this for inline containing blocks
include:

1. We currently store an accumulated relative offset in
NGContainingBlock inside the OOF node, which is any relative offset from
the containing block to the fragmentation context root. We also need to
store an accumulated relative offset from the inline container to the
containing block in order to properly apply all relative offsets at the
time of fragmentation.

A new struct, NGInlineContainer, was added to the OOF node to hold the
inline container object and the accumulated relative offset to the
containing block.

2. A relative offset was also added to the InlineContainingBlockGeometry
struct so that we have access to the relative offset from #1 when
creating the ContainingBlockInfo for the inline container.

3. The way that relative offsets are applied to inlines, it didn't seem
straightforward to separate the relative offset from the normal
offset, like we had in CL:2851595. Instead, store the relative offset
for the inline and subtract it out from the OOF static position once
it reaches the containing block, and subtract it from the containing
block rect offset when determining the ContainingBlockInfo for the
inline container.

4. Store the total relative offset (from the inline container to the
fragmentation context root) in ContainingBlockInfo. This relative
offset will then be applied after fragmentation is complete for the OOF
as a result of CL:2851595.

Bug: 1079031
Change-Id: I7198fec4c01e05ca54c51b2f215569b75b0b869e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2995308


Commit-Queue: Alison Maher <almaher@microsoft.com>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#902060}

--

wpt-commits: 67a78f560e0e0ec601193aa78d7031937bce78f7
wpt-pr: 29548

Automatic update from web-platform-tests
Deflake playing-an-animation.html

The root cause of the flakiness seems to be a floating point
precision issue. This CL fixed it by introducing an epsilon.

Without this fix, I can repro the flakiness locally very easily.
With this fix, I have ran 1000 times with running 48 content
shell in parallel and there is no flake.

Bug: 1198515
Change-Id: I6eaddebe12bba5131ee340549f84b7b27b729c37
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3027227


Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#902034}

--

wpt-commits: a1cb55f97a641485a96cf61766cdf926775813d6
wpt-pr: 29665

Automatic update from web-platform-tests
Deflake WPT test: none.https.html

The failing subtest was identified by:
https://chromium-review.googlesource.com/c/chromium/src/+/3015334

This patch puts the culprit into its own file, and tries to make it work
reliably.

Bug: 1013596
Fixed: 1013596
Change-Id: Ie98b5554824cee35f1e9f671a9962ba993a8b674
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3021142


Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Antonio Sartori <antoniosartori@chromium.org>
Cr-Commit-Position: refs/heads/master@{#901978}

--

wpt-commits: d2a0a6a108413e945e253b0f0493e718637dce09
wpt-pr: 29649

Automatic update from web-platform-tests
Deflake popup-coop-by-sw-from-coop.https.html

Nobody has ever been able to reproduce the problem. It is apparently a
timeout. To fix this, the test is marked as "long" and every subtest are
run separately.

At best, this fixes the issue. At worst, this will give us useful
information: which subtest is the culprit.

Bug: 1151555
Change-Id: I4b62b1d6a96fed97458567b11d7301f60bf6fc77
Fixed: 1151555
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3030564


Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Antonio Sartori <antoniosartori@chromium.org>
Cr-Commit-Position: refs/heads/master@{#901959}

--

wpt-commits: c13cf37f470fb729335ac67d325de63669a1bf1a
wpt-pr: 29675

Bug 1720690 [wpt PR 29676] - Revert "Composite multiple independent transform property animations", a=testonly

Automatic update from web-platform-tests
Revert "Composite multiple independent transform property animations"

This reverts commit 0dfc7e362b3a4fbe98b4dd0afc05206f4213fa69.

Reason for revert: perf regression (crbug.com/1229374)

Original change's description:
> Composite multiple independent transform property animations
>
> Previously, individual transform properties were lumped together with
> transform lists, and only a single transform could be composited. With
> this patch, we support multiple transforms as long as each affects a
> different property (transform, translate, rotate, or scale).
>
> Bug: 696374
> Change-Id: Id4da5da2fceb929bd5ddbffc04f9d63f9b85497a
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3016295


> Reviewed-by: Robert Flack <flackr@chromium.org>
> Commit-Queue: Kevin Ellis <kevers@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#901495}

Bug: 696374
Change-Id: Ic15583885f754916c647363f7eaaf4c39e2072af
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3031641


Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#901930}

--

wpt-commits: 41c2a732e7a325c8705439894b567c30f2c4be64
wpt-pr: 29676

Bug 1715623 [wpt PR 29315] - webcodecs: Updating VPX and MF encoders to heed the VBR setting, a=testonly

Automatic update from web-platform-tests
webcodecs: Updating VPX and MF encoders to heed the VBR setting

Bug: 1217840
Change-Id: I9067e6a690f1f9634d1bcf3f6d5c7e0a469cff27
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2946127


Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Eugene Zemtsov <eugene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#901884}

--

wpt-commits: b00170f86bf1bf4a368003b694f5506f011706c4
wpt-pr: 29315

wpt-pr: 29651
wpt-type: metadata

Automatic update from web-platform-tests
[VirtualKeyboard] Add Secure Context to VK interface.

Added SecureContext to VK interface as we don't want to show/hide VK
when the document isn't the active document and hasn't been
authenticated. Some tests that used to run on insecure context were
changed to now use secure context instead. Using secure context also
led to removal of some tests where we were manually injecting VK
events to the browser. The embedded test server usage causes the
input method initialized in the RWHVA to use the real input method
instead of the mock implementation.
WPT tests in crrev.com/c/2993938 cover those cases.
Spec: https://github.com/w3c/editing/blob/gh-pages/docs/virtualkeyboard/index.html

Bug: 856269

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


Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Keith Lee <keithlee@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Commit-Queue: Anupam Snigdha <snianu@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#901863}

--

wpt-commits: 35593dd1a0617be0adc6428fe0487b34398d28aa
wpt-pr: 29651