Allow new gesture scroll during snap animation

This patch fixes the issue in the linked bug by having InputHandler
de-latch at the start of a snap animation rather than at the end.
This allows a new gesture to latch onto a different scroll node
while the previous scroll node's snap animation is in progress.

In the unit test TrackAnimatingSnapTargetIds, a ScrollBegin call is
added to eschew violating the last_latched_scroll_type_ DCHECK[1] in
InputHandler::ScrollLatchedScroller.

[1] https://source.chromium.org/chromium/chromium/src/+/89812f5b31e3f078d2b0fa9c32904e7424c87cd9:cc/input/input_handler.cc;l=1786

Bug: 333708040
Change-Id: I7571a09644433ebea051a994935a987fdb25e704
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5826968
Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: David Awogbemila <awogbemila@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1377084}

Refactor slow tests in css/css-transitions.

Very wasteful to simply let the animations run given the sheer number
of animations. This batch of tests also liberally uses setTimeout,
which is no longer permitted in WPT tests.

Added a step to catch when all transitions have started, then simply
sample the computed value at fixed values for animation.currentTime.
The animations are left running with currentTime aligned with the
end of the transition, which makes the transitionend events imminent.

Rather than time based, each step in the batch processing is promise
based.

Bug: 375377010,375587482

Change-Id: I8a071a9c5e0c99770d91acb24c8b67a745ace616
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5979045
Reviewed-by: Olga Gerchikov <gerchiko@microsoft.com>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1377078}

[layout] More 'stretch' keyword tests

Just some wpt tests for auto margins and indefinite available space.

No behavior changes.

Change-Id: I3f8bd0b769646db3d16f6672b1ab131c97f1a420
Bug: 41253915
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5983888
Reviewed-by: David Baron <dbaron@chromium.org>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1377013}

Reland "Implement support for bidNonce and seller nonces"

This reverts commit 6eadc638a91b711d4d0037756bf86208717ef7cc.

Reason for revert: Enables the flag on all platforms in the fixture, fixing broken tests.

Original change's description:
> Revert "Implement support for bidNonce and seller nonces"
>
> This reverts commit 803a93609b702479399a8376bd90b1d7780d2794.
>
> Reason for revert: Deterministic failures of browser tests linked to the seller nonce on the bots.
>
> E.g.
> https://ci.chromium.org/ui/p/chromium/builders/ci/fuchsia-arm64-cast-receiver-rel/18747/overview
> https://ci.chromium.org/ui/p/chrome/builders/ci/linux-chromeos-chrome
>
>
> Original change's description:
> > Implement support for bidNonce and seller nonces
> >
> > Introduce a mechanism that allows sellers to avoid giving the same nonce
> > to all buyers, since this can be used to determine that these buyers are
> > in the same auction. Instead, a new nonce is given to each buyer based
> > on the SHA-256 combination of both the auctionNonce and a new seller
> > nonce, which is given to the browser, but not to buyers.
> >
> > The browser can verify the bidNonce from bids by computing the expected
> > bidNonce for a given auctionNonce and seller nonce, thus preserving the
> > existing replay protections of the auctionNonce.
> >
> > Bug: 40275797
> > Fuchsia-Binary-Size: Size increase is unavoidable.
> > Change-Id: I9f2a6117891b30c33cc6831c63f6622faf6f55f1
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5905479
> > Reviewed-by: Orr Bernstein <orrb@google.com>
> > Reviewed-by: Mike Taylor <miketaylr@chromium.org>
> > Reviewed-by: Brendon Tiszka <tiszka@chromium.org>
> > Commit-Queue: Caleb Raitto <caraitto@chromium.org>
> > Cr-Commit-Position: refs/heads/main@{#1376464}
>
> Bug: 40275797
> Change-Id: I61e65f1f7fc7ecb732f49d8860e3976a0fd5cd2a
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5979680
> Reviewed-by: Orr Bernstein <orrb@google.com>
> Commit-Queue: Liviu Tinta <liviutinta@chromium.org>
> Reviewed-by: Mike Taylor <miketaylr@chromium.org>
> Auto-Submit: Liviu Tinta <liviutinta@chromium.org>
> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
> Owners-Override: Liviu Tinta <liviutinta@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1376577}

Bug: 40275797
Change-Id: I176715ba56c94468a3a47522d020439fcf5615d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5979020
Reviewed-by: Mike Taylor <miketaylr@chromium.org>
Commit-Queue: Caleb Raitto <caraitto@chromium.org>
Reviewed-by: Orr Bernstein <orrb@google.com>
Reviewed-by: Brendon Tiszka <tiszka@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1376899}

[nesting] Improve WPT coverage for top-level '&' specificity

The '&' selector, when it has no parent selector to draw from,
has a specificity of zero [1].

Blink already does the right thing. This CL just adds a new WPT
to enforce that behavior, and adjusts an existing tests which
expected specificity to be added.

[1] w3c/csswg-drafts#10196

Bug: 343794754
Change-Id: I3bfdba8a5db66be2d2cdd6f1b2f41b86aadbab9b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5982912
Reviewed-by: Steinar H Gunderson <sesse@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1376861}

Don't update counters in UpdateStyleAndLayoutTreeForContainer

They will be updated later anyway in
LocalFrameView::UpdateStyleAndLayout() and it crashes if, as
marking LayoutObject chain as dirty can ascend above the container
ancestor.

Fixed: 374683348
Change-Id: I672ab81b796c6289cf9267372db6dd2bcd913e40
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5978489
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Daniil Sakhapov <sakhapov@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1376849}

[@container] Improve assert_implements for container-types

Use separate assertions for size, scroll-state, and style queries.

Since style queries are not detectable through CSS.supports, use
serialization of <general-enclosed> for now.

Change-Id: Ia2ebd2b19ae25af3bd7a2ad6b77133e496f0c46e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5979992
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1376840}

[MediaCapabilities] Change WebRTC WPT tests to .any

The WPT tests for MediaCapabilities with type webrtc
have not been run on worker threads.

* Change name of test files to .any.js.
* Replace RTCRtpReceiver and RTCRtpSender with hardcoded
  values if run on worker.

Bug: None
Change-Id: Id0254b7f0eb23f35e5304c1c5a9e9b22332c10bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5979516
Commit-Queue: Johannes Kron <kron@chromium.org>
Reviewed-by: Evan Shrubsole <eshr@google.com>
Cr-Commit-Position: refs/heads/main@{#1376827}

Add more tests to supports-at-rule.tentative.html.

Change-Id: Ib8624def068526e9cb1a9c1a8981922dfbd37588
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5980766
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Steinar H Gunderson <sesse@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1376866}

webnn: Support quantize and dequantize in tflite converter

Implement WebNN quantize operation with TFLite QUANTIZE builtin
operator, only scalar zero point and scale can be supported at
current stage.

The dequantize operation is implemented with TFLite DEQUANTIZE
builtin operator, and emulate the unsupported case with the expression
`output = (input - zeroPoint) * scale`.

Bug: 40206287
Change-Id: Ifea831b0fdb95dd33147310175c8c089ee0a341a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5967060
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: ningxin hu <ningxin.hu@intel.com>
Commit-Queue: Junwei Fu <junwei.fu@intel.com>
Cr-Commit-Position: refs/heads/main@{#1376810}