merge_pr_50918

Bump docker/build-push-action from 6.13.0 to 6.14.0 (#50918)

Bumps docker/build-push-action from 6.13.0 to 6.14.0.

• Release notes
• Commits

---

updated-dependencies:

• dependency-name: docker/build-push-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
  ...

Signed-off-by: dependabot[bot] support@github.com
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

merge_pr_50868

Allow multi-files variants to have no parameters in canvas WPT generator

It was already possible to have variants without parameters, but it was
only working for single-file variant layout. This CL fixed it for
multi-files, allowing tests like:

• name: 2d.example-empty-params
  code: ctx.globalCompositeOperation = {{ variant_name }};
  variants:
  • source-over:
    source-in:
    source-out:

Change-Id: Ibf4584cb693f8e2aa2a1dc432baf303c98812cbe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6227183
Reviewed-by: Aaron Krajeski aaronhk@chromium.org
Commit-Queue: Jean-Philippe Gravel jpgravel@chromium.org
Cr-Commit-Position: refs/heads/main@{#1424216}

merge_pr_50919

WebNN: Don't run per-op WPTs in non-window contexts

The WebNN tests are written as ".any.js" tests which can run in both
Window and Worker contexts. This is great! But we running every test
on every combination of (CPU, GPU, NPU) x (Window, Worker) consumes
significant cycles for little benefit. While tests and various backend
and platform implementations are in flux, it also adds significant
burden to gardeners.

Scope down to running just the Window variations for op-specific
tests. Tests for things like inputs, constants, tensors, and object
lifecycles are still run in all contexts, and identity() is retained
as a "canary".

Change-Id: I1f1c749ea4d002a578d6d2ca89579cec6b0090e2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6299831
Reviewed-by: Weizhong Xia weizhong@google.com
Commit-Queue: Weizhong Xia weizhong@google.com
Auto-Submit: Joshua Bell jsbell@chromium.org
Reviewed-by: Reilly Grant reillyg@chromium.org
Cr-Commit-Position: refs/heads/main@{#1424187}

merge_pr_50914

LoAF: Set source line and column for promise-resolver

The LongAnimationFrameSourceLineColumn runtime flag was introduced
to enable the sourceLine and sourceColumn properties in PerformanceScriptTiming:
https://chromium-review.googlesource.com/c/chromium/src/+/6188741

This CL extends support for this feature to promise resolvers.

• web_tests/external/wpt/long-animation-frame/tentative/loaf-source-location.html

Bug: 391417815
Test:
Change-Id: I8811cf9afe824734cc88b7e94a319662b47d11e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6268279
Commit-Queue: Joone Hur joonehur@microsoft.com
Reviewed-by: Noam Rosenthal nrosenthal@chromium.org
Reviewed-by: Nate Chapin japhet@chromium.org
Cr-Commit-Position: refs/heads/main@{#1424190}

merge_pr_50912

[anchor] Anchor recalculation point when switching fallbacks.

The spec says that an anchor recalculation point occurs when switching
to a different anchor positioning option, and not just when the element
gets displayed for the first time.

In order to support this, we need to stay at the same position option as
long as it fits, rather than considering all fallback alternatives every
time an anchor-positioned box is being laid out. Only do that when the
current option doesn't fit.

See https://drafts.csswg.org/css-anchor-position/#fallback-apply

This will introduce some statefulness, in that the current scroll offset
alone doesn't determine which position option is used: It depends on how
we got to that scroll offset, i.e. where we came from. Add a test to
demonstrate this, and fix some existing tests to pass with the new
behavior.

Behavior behind runtime flag CSSAnchorPositionAreaVisualPosition.

Bug: 391907168, 373874012
Change-Id: I7b7f81d5d7a9009508eda03234f760bdfb7cd6f9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6198263
Reviewed-by: Rune Lillesveen futhark@chromium.org
Commit-Queue: Morten Stenshorne mstensho@chromium.org
Reviewed-by: David Grogan dgrogan@chromium.org
Cr-Commit-Position: refs/heads/main@{#1424129}

merge_pr_50911

Remove stale TODO about isolation nodes and fragmentation.

Fragmented isolation nodes have been allowed ever since LayoutNG block
fragmentation got introduced. Include a test that should have failed if
this wasn't implemented correctly.

The code that checked for fragmentation got removed here:
https://chromium-review.googlesource.com/c/chromium/src/+/4804328

Bug: 40596162
Change-Id: Ia6a52298ca107528a0c17c4c82b933065505cbef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6298808
Commit-Queue: Morten Stenshorne mstensho@chromium.org
Reviewed-by: Xianzhu Wang wangxianzhu@chromium.org
Reviewed-by: Vladimir Levin vmpstr@chromium.org
Cr-Commit-Position: refs/heads/main@{#1424102}

merge_pr_50910

Prevent customizable select :focus-visible with mouse

This patch prevents select:focus-visible from matching when using the
mouse for customizable selects. appearance:auto selects will continue to
match :focus-visible when being clicked for now.

Bug: 393978931
Change-Id: Ic6c530a30cfc626564bcf041d9bf27f708675f52
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6221486
Reviewed-by: Traian Captan tcaptan@chromium.org
Commit-Queue: Joey Arhar jarhar@chromium.org
Cr-Commit-Position: refs/heads/main@{#1424080}

merge_pr_50909

[Blob URL] Add more delay to second iframe in subframe partitioning test

Hopefully this will help cut down on the remaining flakiness in the
test.

Bug: 390049422
Change-Id: Ife67023670f110563441ba6bf52b0c7e7e719333
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6293167
Commit-Queue: Andrew Williams awillia@chromium.org
Reviewed-by: Janice Liu janiceliu@chromium.org
Cr-Commit-Position: refs/heads/main@{#1424053}

merge_pr_50907

[functions] Let parameter defaults reference other parameters

Per "evaluate a custom function" [1], the default value of a parameter
may "see" other parameters, e.g. @function --f(--x, --y:var(--x)).
Before this CL, that var(--x) would resolve in the outer scope,
but now it's supposed to resolve against the actual argument value
passed for --x. At the same time, default values should not have
access to the actual locals of the function body, meaning that
they resolve in some gray area between the outer scope and inner
scope.

In this CL, that "gray area" is implemented by using a disposable
FunctionContext with the unresolved defaults set as the unresolved
locals. This is convenient, because we get all the needed "dependency
handling" (including cycle detection) for free.

Since various things now need to parse against a type (arguments,
defaults, and the 'result' descriptor), and because these various
things differ in how they are represented (some CSSVariableData,
some StringView), this CL aligns all of those things to use
CSSVariableData, and adjusts ResolveFunctionExpression accordingly.
This would be needed anyway, to actually transport various tainting
information, though that is not explicit handled/tested in this CL.

Finally, note that there is a drive-by fix in this CL: the "already
applied" branch of ApplyLocalVariables now actually skips the work
if it's already applied. This should ideally have a performance test,
which is tracked as a follow-up task (Issue 397164440).

[1] https://drafts.csswg.org/css-mixins-1/#evaluate-a-custom-function

Fixed: 397459622
Bug: 325504770, 397164440
Change-Id: Ic705209d25f4bee6149f2397bda78e1224b16901
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6276516
Commit-Queue: Anders Hartvoll Ruud andruud@chromium.org
Reviewed-by: Steinar H Gunderson sesse@chromium.org
Cr-Commit-Position: refs/heads/main@{#1423855}

merge_pr_50906

[functions] Ensure that referenced var in outer scope is applied

Dynamic scoping allows a var() to see local variables defined
higher up the call stack. If a local variable in some outer function
makes a function call, that inner function call may reference variables
in the outer function that are not yet resolved (i.e. do not yet
exist on FunctionContext::locals). We already handle this for references
within the same frame. Fixed by calling LookupAndApplyLocalVariable
on each frame visited during var()-dereferencing.

This has implications for cycle detection too, but that's not handled
in this CL (Issue 397485310).

Bug: 325504770, 397620596
Change-Id: I4aad9eeb885d19ccba116b89f40faf0cc721201c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6287713
Reviewed-by: Steinar H Gunderson sesse@chromium.org
Commit-Queue: Anders Hartvoll Ruud andruud@chromium.org
Cr-Commit-Position: refs/heads/main@{#1423847}