merge_pr_44218

[masonry] Track Sizing Updates

This patch is a pass at fixing some of the track sizing masonry test cases.
This is an export of WebKit WPT local changes.

merge_pr_43702

Map flexbox tests to web-features (#43702)

This includes tests for flex gap which should ideally be mapped to
flexbox-gap, but that's not easy to do without the tests being mapped to
both features at the same time, since most tests are in the same
directory and there's no support for exclusions. A TODO describes the
situation.

merge_pr_45773

Make cross-origin-ancestor-activeelement-after-child-lose-focus.sub.html more robust.

This makes two changes to try to make the test
cross-origin-ancestor-activeelement-after-child-lose-focus.sub.html more
robust:

• It checks the message data in case postMessage is used by something
  else in WPT (although I think this is unlikely), to make sure that the
  message received is the one intended (that is sent by the subframe's
  subframe).
• It makes the subframe's subframe wait until load before focusing its
  input, on the theory that it might be possible that this focusing is
  happening too early to be effective.

My hope is that these might fix the test being flaky in Chromium CI.

Bug: 332068449
Change-Id: Idf70ba87a8559223f9dff7900cadca9ea56126e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5464001
Auto-Submit: David Baron dbaron@chromium.org
Commit-Queue: Di Zhang dizhangg@chromium.org
Reviewed-by: Di Zhang dizhangg@chromium.org
Cr-Commit-Position: refs/heads/main@{#1288995}

merge_pr_45770

Remove waiting for focus change that didn't fix test flakiness.

This reverts the two previous changes to this test, to wait longer for a
focus change, because they didn't fix the test being flaky in Chromium
CI.

Bug: 332068449
Change-Id: Ib0c21a236044af0eee2bff2f4b24e5f1f90de867
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5463426
Commit-Queue: Di Zhang dizhangg@chromium.org
Reviewed-by: Di Zhang dizhangg@chromium.org
Auto-Submit: David Baron dbaron@chromium.org
Cr-Commit-Position: refs/heads/main@{#1288976}

merge_pr_45767

Revert "Enable MediaRecorderEnableMp4Muxer as default."

This reverts commit 8b14d30eb8647a87b2fdc567d5b97f3ad1021b00.

Reason for revert: introduces consistently failing test

Bug: 335477326

Original change's description:

Enable MediaRecorderEnableMp4Muxer as default.

It enables the MP4 mimetype for MediaRecorder.

It supports codecs of h264 (avc1), aac (mp4a.40.2), vp9, Opus. The default is vp9 and Opus.

It supports all platforms, even without proprietary OS where VP9 and Opus codecs can be used.

It updates the web platform tests.

(It is nice to have this CL first in, https://chromium-review.googlesource.com/c/chromium/src/+/5337945)

Bug: 40127044
Change-Id: If8533997f4ee97d40085888496e5b80cc8cc7675
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5350767
Reviewed-by: Markus Handell handellm@google.com
Commit-Queue: Sunggook Chue sunggch@microsoft.com
Reviewed-by: Dale Curtis dalecurtis@chromium.org
Cr-Commit-Position: refs/heads/main@{#1288869}

Bug: 40127044
Change-Id: Ic2f235ae37585bac2c3a0d72dd377c5a8cd9439e
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5462323
Owners-Override: Nicolás Peña npm@chromium.org
Auto-Submit: Nicolás Peña npm@chromium.org
Commit-Queue: Nicolás Peña npm@chromium.org
Bot-Commit: Rubber Stamper rubber-stamper@appspot.gserviceaccount.com
Cr-Commit-Position: refs/heads/main@{#1288928}

merge_pr_45762

[anchor] Delay ::backdrop updates during interleaving

Elements in the top layer appear early in the layout tree,
and so we get the call to UpdateStyleForOutOfFlow for ::backdrop
before the call to UpdateStyleForOutOfFlow for the originating
element. This is problematic, because the second call to UpdateStyleForOutOfFlow (for the originating element) may also
recalc the style of the ::backdrop pseudo-element (which already
had its UpdateStyleForOutOfFlow call). The result is a computed
style for ::backdrop where all anchor*() functions are invalid.

This issue is currently masked by a combination of CL:5447517 and
Issue 330758160: the second call to UpdateStyleForOutOfFlow
recalculates the style, but doesn't invalidate anything.
Since the computed value of an invalid anchor*() is auto (CL:5447517),
getComputedStyle() grabs the value from the box, which is still correct
due to missing invalidation.

However, if we add explicit 0px fallbacks to the anchor() functions
within ::backdrop, getComputedStyle() won't ask the box, and we see
that the computed values are in fact wrong.

This problem is similar to the issues with had with ::backdrop for
Container Queries, so we can solve this the same way: by delaying
the updates to ::backdrop using PostStyleUpdateScope, and do another
round if needed.

Note: The new test (position-try-backdrop.html) also passes without
this CL. The anchor attribute test no longer passes without this CL
however, due to the addition of explicit 0px fallbacks (which aren't
supposed to be taken).

Bug: 335052779
Change-Id: I48f33568e172983be28264a982b5e04c22e16001
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5458187
Commit-Queue: Anders Hartvoll Ruud andruud@chromium.org
Reviewed-by: Rune Lillesveen futhark@chromium.org
Cr-Commit-Position: refs/heads/main@{#1288929}

merge_pr_45760

Bump wptserve to version 4.0.2

merge_pr_45756

Remove erroneous ref from event-pseudo-name.html (#45756)

This test fails in WebKit because it is a testharness.js test and also tries to compare itself to a reference file that doesn't use testharness.js.

merge_pr_45747

Deflake attempt for fenced frame null config -> about:blank WPT

There are a few things wrong with this test (I was relatively new
to WPTs when I wrote it):

1. attachFencedFrameContext had no await, meaning that there
   is no guarantee that the frame context exists before operating on it.
   I'm assuming this is the reason for most of the failures, and have
   fixed it.
2. The test had a probably-unnecessarily-long timeout, which I cut in
   half to 1.5s
3. There was no meta timeout tag, which I've added just in case the
   1.5s timeout causes breakage on slower builders.

I know that timeouts in tests are not ideal, but this test relies on
one because all other code that could be used to observe the fenced
frame is removed when navigating to about:blank.

Bug: 333501264
Change-Id: Ia54c69bde836f0b6bcb06a4cb1863d9de1d1c5e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5459098
Reviewed-by: Liam Brady lbrady@google.com
Commit-Queue: Andrew Verge averge@chromium.org
Cr-Commit-Position: refs/heads/main@{#1288725}

merge_pr_45741

Correct the selection color over a highlight

Selection was not correctly accounting for the color fallback in
highlight overlays. Fix the issue by using the same color
resolution methodology as other highlights.

Fixed: 40264572
Change-Id: If5450fcca609e4a3c56dcc24e5f22d7381bd8fcc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5455259
Commit-Queue: Stephen Chenney schenney@chromium.org
Reviewed-by: Fredrik Söderquist fs@opera.com
Cr-Commit-Position: refs/heads/main@{#1288924}