FLEDGE: Make B&A WPT tests more hermetic

...by making sure to always explicitly use a .test coordinator.

Bug: 383600441
Change-Id: Ib163b5042ebfdb04d906c9bd549f323cbed45768
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6094505
Reviewed-by: Mason Freed <masonf@chromium.org>
Reviewed-by: Russ Hamilton <behamilton@google.com>
Commit-Queue: Maks Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1399474}

webnn: add wpt for bidirectional lstm

Fixes some minor bugs with CoreML bidrection implementation.

Also adjusted ULP for this complex op to 3, this is same as gru.

Bug: 360052663
Change-Id: Ie15ab15a359be70e219fd61ee0d3a3fea21f3405
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6103076
Commit-Queue: Phillis Tang <phillis@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1399398}

DOM: Test 'slotchange' event firing during move

See whatwg/dom#1307 (comment).

R=nrosenthal@chromium.org

Bug: 40150299
Change-Id: I9529941e05591620da5b3c11635693a15f0ce866
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6111212
Reviewed-by: Noam Rosenthal <nrosenthal@chromium.org>
Commit-Queue: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1399350}

Update Wasm tests (web-platform-tests#49809)

* Update Wasm tests

* Ignore linting errors in automatically imported Wasm tests

---------

Co-authored-by: wpt-pr-bot <wpt-pr-bot@users.noreply.github.com>
Co-authored-by: Panos Astithas <pastithas@google.com>

Only update first appended <selectedcontent> element

Since we are only planning to support one <selectedcontent> element in
<select>, this patch only performs a clone into the first
<selectedcontent> in tree order.

This is in response to feedback here:
whatwg/html#10633 (comment)

This patch also removes the logic which clears <selectedcontent>
elements when they are removed/disconnected.

Change-Id: I1580ec9f12df463d1f5134905e3e527cfefa694d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6043186
Reviewed-by: David Baron <dbaron@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1399301}

[carousel] Implement targeted scroll-marker selection for ::column

::column pseudos[1] may create ::scroll-markers, but do not exist in the
DOM tree as parents of the elements which are flowed into them.
They also do not appear to have LayoutObjects and are not found[2]
in the layout tree. So, when searching for the appropriate scroll-marker
to select for a targeted scroll we need to consider whether the
scroll-marker-generating element (marker-generating-element) found in
the layout tree is also flowed into the same scroll-marker-generating
::column (marker-generating-column) as the target of the scrollIntoView
operation. If the target and marker-generating-element are both in
marker-generating-column, marker-generating-element is the preferred[3]
choice. The only means we have of checking whether an element is flowed
into a ::column is by looking at the rect associated with that ::column.

[1] https://drafts.csswg.org/css-multicol-2/#column-pseudo
[2] https://source.chromium.org/chromium/chromium/src/+/165f5ddad25b289f886a248ca810d075b1e7bb87:third_party/blink/renderer/core/page/scrolling/snap_coordinator.cc;l=254-255
[3] w3c/csswg-drafts#10738 (comment)

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

[carousel] Pin the selected scroll-marker for targeted scrolls

The CSS working group resolved[1] that when a scroll operation is aimed
at an element, i.e. Element.scrollIntoView, the associated
scroll-marker-group should select the active scroll-marker based on the
element which the operation is intending to scroll to. In such cases,
the scroll-marker that should be selected is the scroll-marker
associated with the first scroll target (a scroll target is an element
which generates a scroll-marker) found through a search starting from
the target of the scrollIntoView itself and backwards in tree-order.
As soon as some other type of scroll occurs, e.g. Element.scrollTo, or
a user gesture scroll, the scroll-marker-group should no longer
consider its active marker pinned, i.e. it should be based on the
scroll position.

This patch implements this for elements in general, but not for
::column pseudo elements which may also act as scroll targets since
::column::scroll-marker is allowed. The ::column case needs to be
handled specially as ::column pseudos are not parents of the elements
which are flowed into them in the DOM tree. This will be done in a
follow-up patch.

[1] w3c/csswg-drafts#10738 (comment)

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

[css-properties-values-api] Split some of the registerProperty tests …

…about sign() with mixed lengths.

Closes web-platform-tests/interop#911

[carousel] Move ::column and ::column::scroll-marker tests to WPT

As the spec for these pseudo elements is mature enough and passed
a few reviews, not making them .tentative.

Bug: 365680822
Change-Id: I25a9b9be9392eca1af8b99c21de9539f8415aeb1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6111372
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Auto-Submit: Daniil Sakhapov <sakhapov@chromium.org>
Commit-Queue: Daniil Sakhapov <sakhapov@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1399112}

Paint nothing when feImage references svg inlines

The spec states that non-image feImage references should be rendered
"according to the behavior of the use element"
(https://drafts.fxtf.org/filter-effects/#feImageElement), which is
nothing for the case of a standalone tspan.

Fixed: 383187487
Change-Id: If3f8438676c593f6e9aab4f879ea9212a0806621
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6111507
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1399218}