merge_pr_50209

Reland "[fetch-later] Implement "available deferred fetch quota"1" (#50209)

This is a reland of commit 3d1f2a7dbc93c009ed9bccc923d187301f99ca64

The failure from external/wpt/fetch/fetch-later/new-window.tentative.https.window.html was caused by:

• Incorrect use of for... in loop iteration. Should be for...of.
• noopener window cannot communicate back to opener, so there is no
  way for opener to reliably wait for it. Removed it from the loop.

Original change's description:

[fetch-later] Implement "available deferred fetch quota"1

And update "Deferred fetch quota" implementation in
FetchManager to use the algorithm.

Also turn on use_deferred_fetch_policy to enable the whole quota
logic in OT.

Bug: 40276121
Change-Id: I0892c6e5c98aba48ef0f1155edba8c6d78258aec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5599362
Commit-Queue: Ming-Ying Chung [email protected]
Reviewed-by: Adam Rice [email protected]
Cr-Commit-Position: refs/heads/main@{#1408824}

Bug: 40276121
Change-Id: I1f3ecb179c7733dde86d70f3d904821c12d2c6af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6187615
Commit-Queue: Ming-Ying Chung [email protected]
Reviewed-by: Adam Rice [email protected]
Cr-Commit-Position: refs/heads/main@{#1409502}

Co-authored-by: Ming-Ying Chung [email protected]

merge_pr_50207

[wdspec] Increase time range for BiDi network events timing assertions

Adds a helper to compute time range for BiDi network event timings assertions and
increases the allowed range by 100ms instead of 1ms to avoid intermittent issues on windows CI.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1942664
gecko-commit: 4645596600ce8b0fdb451f1be39c13465f699d3e
gecko-reviewers: webdriver-reviewers, Sasha

merge_pr_50226

Fix old html.css selectors for popover/dialog

When the overlay property was added, these rules should have
changed to simply look at whether the popover is a) a popover, and
b) in the top layer. This CL fixes a bug where it was possible for
a to be in the top layer, but not have the
overlay:auto property, which caused painting issues.

Fixed: 388538944
Change-Id: I9665daef9f33ae61ea7bf82cb18429f14dab7d86
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6185344
Reviewed-by: Joey Arhar [email protected]
Commit-Queue: Joey Arhar [email protected]
Auto-Submit: Mason Freed [email protected]
Cr-Commit-Position: refs/heads/main@{#1409844}

merge_pr_50225

Implement parsing for animation-trigger-{exit-}range shorthands

The spec is currently a work-in-progress[1] but this comment[2]
describes the API.

[1] w3c/csswg-drafts#10128
[2] w3c/csswg-drafts#8942 (comment)

Bug: 390314945
Change-Id: I2c335d6be7b6e264fb1cbf4ae4cc3fa9aedc9136
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6187119
Reviewed-by: Anders Hartvoll Ruud [email protected]
Commit-Queue: David Awogbemila [email protected]
Cr-Commit-Position: refs/heads/main@{#1409968}

merge_pr_50223

[rust png] De-flake toBlob-cross-realm-callback-report-exception test.

Before this CL, the test assumed that frames[1].onerror will be called
within 25ms. It seems that after switching to the Rust PNG encoder this
doesn't always happen. So after this CL:

1. The test will wait until at least one frames[i].onerror happens
   (with a timeout of 3s). This is expected to make the test more
   robust and less flaky.
2. Only afterward the test will wait an additional 25ms to see if
   unexpectedly any other onerror has fired. This part may continue
   to be flaky, but this CL doesn't make this worse... :-/

Bug: chromium:383580201
Change-Id: Icc4c5a1bc433bb3b9401108eefe35d0dc639cd58
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6182295
Reviewed-by: Florin Malita [email protected]
Commit-Queue: Łukasz Anforowicz [email protected]
Cr-Commit-Position: refs/heads/main@{#1409833}

merge_pr_50222

Add tasks for gain/lose interest on interesttarget [2/N]

This CL changes the behavior of gaining and losing interest such that
both are scheduled as tasks, optionally with CSS-driven delays. That
not only adds the native ability to control those delays (which, per
the conversation at [1], seems important) but also this resolves
some interesting behavior even when the delays are zero:

• position the popover on top of the interest invoker
• show interest, via hover, on the interest invoker
  --> that will invoke the target popover
• the target obscures the invoker, which immediately triggers the
  loss of interest on the invoker, and that closes the popover

Bug: 326681249
Change-Id: I88d1cdaf975d56b819a0ff93cc8a48c2c5d71649
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6175776
Reviewed-by: David Baron [email protected]
Commit-Queue: Mason Freed [email protected]
Auto-Submit: Mason Freed [email protected]
Cr-Commit-Position: refs/heads/main@{#1409860}

merge_pr_50221

Make ::scroll-button disabled state snap aware

Scroll buttons should be disabled when snapping prevents any further scrolling
in their intended direction.

Bug: 388545125
Change-Id: I5991f2ff02965a2495a7507d74504b3f213f2657
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6180126
Reviewed-by: Vladimir Levin [email protected]
Reviewed-by: Daniil Sakhapov [email protected]
Commit-Queue: Robert Flack [email protected]
Cr-Commit-Position: refs/heads/main@{#1409802}

merge_pr_50219

Add WPT for multi-seller getInterestGroupAdAuctionData

Change-Id: Ic65307069147f6325303fc35dfda29f733df6346
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6180162
Commit-Queue: Russ Hamilton [email protected]
Reviewed-by: Qingxin Wu [email protected]
Cr-Commit-Position: refs/heads/main@{#1409702}

merge_pr_50218

Add wpt test for @container affecting after-change style

Bug: 40337057
Change-Id: I3ea0283d2ca9ff4730696afa06a9cc82ddab700e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6175093
Reviewed-by: Anders Hartvoll Ruud [email protected]
Commit-Queue: Rune Lillesveen [email protected]
Cr-Commit-Position: refs/heads/main@{#1409648}

merge_pr_50216

Implement parsing for animation-trigger-range-*

The spec is currently a work-in-progress[1] but this comment[2]
describes the API.

[1] w3c/csswg-drafts#10128
[2] w3c/csswg-drafts#8942 (comment)

Bug: 390314945
Change-Id: I6ac50730653e70219775895c315f91f771ea7c13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6182723
Commit-Queue: David Awogbemila [email protected]
Reviewed-by: Anders Hartvoll Ruud [email protected]
Cr-Commit-Position: refs/heads/main@{#1409620}