merge_pr_46516

[WPT] fix *-policy-frame-policy-timing

Let's re-enable these and try a new fix. Hopefully a real ready signal
will be enough?

Follow up to:
https://chromium-review.googlesource.com/c/chromium/src/+/5537049

Change-Id: Ia67a4e17c941d62d0b37013d8a41271cbb0bc02d
Fixed: 340363659
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5577175
Commit-Queue: Mike Taylor miketaylr@chromium.org
Auto-Submit: Ari Chivukula arichiv@chromium.org
Reviewed-by: Mike Taylor miketaylr@chromium.org
Cr-Commit-Position: refs/heads/main@{#1307576}

merge_pr_46515

IDB WPTs: Run bindings-inject-keys/bindings-inject-values on workers

Currently, the bindings-inject-keys-bypass-* and
bindings-inject-values-bypass-* IndexedDB WPTs only run in a window
environment.This change extends them to also run in dedicated, shared,
and service worker environments.

Bug: 41455766
Change-Id: I8ee7daf2ee8a86de9482eba7690de06f12dfae1d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5567651
Reviewed-by: Evan Stade estade@chromium.org
Commit-Queue: Rahul Singh rahsin@microsoft.com
Cr-Commit-Position: refs/heads/main@{#1307123}

merge_pr_46468

[a11y] Move disputed self/cross-referential aria-labelledby tests to tentative file (#46468)

There is a pending spec discussion surrounding these tests - we're not sure if they're valid
as written, according to the current spec. This commit moves them to a new tentative file
pending resolution of that discussion.

merge_pr_46422

Cred Man: Add fully active checks (#46422)

• Cred Man: Add fully active checks

• Update tests based on feedback

merge_pr_46387

webnn: Migrate argMinMax validation tests to WPTs

This CL adds WPT tests for argMinMax and removes the unit tests
MLGraphBuilderTest.ArgMinMaxTest and MLGraphTestMojo.ArgMinMaxTest.

Bug: 327337526, 328026885
Change-Id: I8fcce0db9e4b1673e721baf0b7abdfe3a06bdf2b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5547296
Reviewed-by: Austin Sullivan asully@chromium.org
Commit-Queue: Shanxing Mei shanxing.mei@intel.com
Reviewed-by: ningxin hu ningxin.hu@intel.com
Cr-Commit-Position: refs/heads/main@{#1307229}

merge_pr_46142

ARIA: Add sectionheader and sectionfooter role tests (#46142)

Adding new roles to .tenative file until implementation is complete

See w3c/aria#1931

merge_pr_46520

Refactor Xr Depth Data to be per view

The WebXR Spec requires that a view be passed in to receive depth data.
The current implementation simply sends depth data alongside with the
rest of the frame data and process it independently in the blink
XrSession. This is fine because the current only platform that supports
depth sensing is ARCore, which only has one View. However, in order to
implement Depth Sensing for OpenXR (which has multiple views), this
needed to be changed to allow sending up data per-view. This required
refactoring the XrDepthManager to be owned by an XrViewData (since the
actual XRView objects are created per-frame and largely wrap this data).
Since XRViewData's can theoretically (though likely not usually done
in practice), be recreated mid session if e.g. the count/order of views
changes, this now requires storing the depth_config in XrSession to
allow for this re-creation. Rather than simply storing the depth config,
this change opts to store the entire device_config and thus remove a
few other unnecessary member variables.

As part of this update to update Depth as part of the XRViews, a few
other refactors were made, as well as some tangientially related
cleanups. A few of these arose because it seemed like it was necessary
to switch XrFrameData to be passed by value rather than const& to steal
the Views and subsequent DepthData off of it. While that turns out to
not have been necessary (because const& to a pointer doesn't prevent
stealing data from the underlying struct...), many of these changes
are left in as it improves both the overall readability and intent
behind the const& and later usage. These other changes are, in general:

• UpdateViews now handles the deferred update logic that happened
  several lines later in views(). This is more consistent with what
  a reader would likely expect from the calls.
• The UpdateViews refactor removes the need to keep the pending_views_
  variable. It is removed, and it's usages updated as appropriate.
• XrDepthManager is no longer exposed to XrSession, so the DepthData and
  DepthFormat strings (that the page receives off of XrSession) now live
  in XrSession.
• The Mojom XrDepthDataUpdated::time_delta member was unused outside of
  the device process, and thus is now removed from the interface.
• XrFrameProvider manually updated some additional state after calling
  UpdatePresentationFrameState. This state was updated regardless of
  session type, and as such was moved inside of
  UpdatePresentationFrameState, to facilitate std::move'ing the
  FrameData to that method. The comments around UpdateFrameState were
  also outdated/indirect and updated/clarified.
  Note that the ordering of some of these additional updates is
  different after this CL.
• XrFrameProvider stored a few variables whose storage seemed to
  now be unnecessary, these variables were removed and their usage
  was ported to closer to where they were needed.
• Because XrFrameProvider no longer needed to split off the VRPosePtr,
  from the FrameData, it was removed as a separate argument to the
  UpdatePresentationFrameState.

Bug: 342213635
Change-Id: I2fd8f3d609e955c84aff2e21b147443aeb987c02
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5565198
Reviewed-by: Brandon Jones bajones@chromium.org
Reviewed-by: Tom Sepez tsepez@chromium.org
Commit-Queue: Alexander Cooper alcooper@chromium.org
Cr-Commit-Position: refs/heads/main@{#1307066}

merge_pr_46514

Clean up anchor attribute display test and test for auto value

The previous test did not exercise the auto keyword within the
anchor() function. The new test ensures auto can be used as a
value for position-anchor but not as a first argument to the
anchor() function.

The spec is here:

https://drafts.csswg.org/css-anchor-position-1/#anchor-pos

Bug: 342579983
Change-Id: I4a2c953496bdbb650db54dcc3e0b8595046f3de6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5569991
Auto-Submit: Mason Freed masonf@chromium.org
Reviewed-by: Joey Arhar jarhar@chromium.org
Commit-Queue: Joey Arhar jarhar@chromium.org
Cr-Commit-Position: refs/heads/main@{#1306864}

merge_pr_46513

Cleanup "check show the picker consumes user activation" (#46513)

Remove bad <select> click() test and fix some syntax errors. Cleanup of #46502.

merge_pr_46512

Map scrollbar-gutter tests to web-features (#46512)