merge_pr_58755

Fix paint offset of inline with backface-visibility:hidden

This fixes the bug when PaintOffsetTranslationForComposited is enabled.
Now don't create PaintOffsetTranslation for a LayoutInline with
backface-visibility:hidden if it doesn't have a self-painting layer.
This is because for now such a LayoutInline doesn't know how to apply
paint properties.

This CL keeps status:"test" for PaintOffsetTranslationForComposited.

It's complex to let inline painting support non-self-painting-layer
paint properties on LayoutInlines because the text fragments don't
have property tree states. Nevertheless, as backface-visibility:hidden
might be the only case, ongoing css discussions about creating
stacking context in the case might be the ultimate solution.

Bug: 455884493, 495746269
Change-Id: I67144314ee1551287be578bef2089a853d7d5194
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7698719
Reviewed-by: Philip Rogers pdr@chromium.org
Commit-Queue: Xianzhu Wang wangxianzhu@chromium.org
Cr-Commit-Position: refs/heads/main@{#1605208}

merge_pr_58705

Add tests for the interraction between viewport units and @page margins (#58705)

Add tests for the interaction between viewport units and @page margins

merge_pr_58677

Add tentative @container/stuck test for post-layout snapshot

Per HTML spec PR[1], run snapshot post-layout state steps is invoked
after layout for each iteration in the resizeObserver loop. Add a
scroll-state() container query test for this.

[1] whatwg/html#11613

Bug: 384523570
Change-Id: Ibf87e93147537b62d1eb888df8b5d357f3d19e39
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7687296
Reviewed-by: Anders Hartvoll Ruud andruud@chromium.org
Commit-Queue: Rune Lillesveen futhark@chromium.org
Cr-Commit-Position: refs/heads/main@{#1603335}

merge_pr_58752

Prompt API: Reject system messages appended after others

Reject appending system messages when sessions have [pending] context.
Run ValidateInput on prompt and append; track imminent pending usage.
Update exception message. Add WPT coverage.

Fixed: 495843316
Change-Id: I77dfb450719e86041c3e1ebea83f0511c3db4e43
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7698599
Auto-Submit: Mike Wasserman msw@chromium.org
Commit-Queue: Mike Wasserman msw@chromium.org
Reviewed-by: Jingyun Liu jingyun@google.com
Cr-Commit-Position: refs/heads/main@{#1605041}

merge_pr_58750

Fix scroll animation range offset zoom handling on write

Setting rangeStart/rangeEnd via the Web Animations API stored px values
in CSS pixels, but the internal coordinate space expects physical pixels
and the read path divides by zoom - causing e.g. 50px at zoom=2 to read
back as 25px.

Apply zoom at the API call sites (Element::animate, setRangeStart,
setRangeEnd) and record the zoom factor used for correct round-tripping
in the read path.

Fixed: 40929569
Change-Id: I7f1b6508ef7ddaea619234aa6fd67f9a82544c56
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7668198
Reviewed-by: Kevin Ellis kevers@chromium.org
Reviewed-by: David A awogbemila@chromium.org
Commit-Queue: jj jj@chromium.org
Cr-Commit-Position: refs/heads/main@{#1605036}

merge_pr_58746

[anchor] Don't use position-area alignment if we have no default anchor

Previously we'd unconditionally compute the alignment if we had
position-area as not "none". This was incorrect we should only be doing
this if we have a default anchor.

Use the existence of PositionAreaOffsets() on the style object to
determine this.

Fixed: 388575663
Change-Id: I906965f75bfc1dcbddb6cbf12f948edcefbd326b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7699195
Reviewed-by: Morten Stenshorne mstensho@chromium.org
Commit-Queue: Ian Kilpatrick ikilpatrick@chromium.org
Cr-Commit-Position: refs/heads/main@{#1604871}

merge_pr_58745

Only run post-layout snapshots in the HTML event loop

UpdateLifecyclePhasesInternal() is invoked in other cases than for the
lifecycle update which is part of the HTML event loop with rendering
updates and running resizeObservers.

For resizeObservers, we handle this by limiting the invocation to when
the target_state is kPaintClean.

For post-layout snapshotting, we did not limit this at all, causing us
to do snapshotting for cases like elementsFromPoint() and hit testing.

This CL does the same limitation with a couple of exceptions:

• Printing uses kPrePaintClean as the target. While we are not running
  resizeObservers for printing, we should run snapshotting for printing
  to render the correct state for initial rendering of scroll-state(),
  scroll-timelines, anchor positioning, etc.

• There are some unit tests using kTest for mid-flight target states
  to test intermediate state.

Bug: 495684789
Change-Id: I3de76badcfc7e760f46628a62ac0cbf331f38ee8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7696995
Reviewed-by: Robert Flack flackr@chromium.org
Commit-Queue: Rune Lillesveen futhark@chromium.org
Cr-Commit-Position: refs/heads/main@{#1604787}

merge_pr_58743

Add lutien to WebDriver suggested reviewers (#58743)

• Add lutien to WebDriver suggested reviewers

• Apply suggestion from @whimboo

• Fix maintainers list by removing duplicates

Removed duplicate entries from the maintainers list.

• Clean up META.yml by removing duplicates

Removed duplicate entries for 'juliandescottes' and adjusted the list.

---

Co-authored-by: Henrik Skupin mail@hskupin.info

merge_pr_58742

[CE] Fix geolocation permission element display style tests

Refactor the wpt tests for geolocation permission element display styles
to prevent flaky failures and timeouts. The previous implementation used
a single async_test that processed all cases simultaneously, often
exceeding the limit of active geolocation elements allowed on a page.

Fixed: 469578374, 494494828
Change-Id: I2f4ead3cc4e22961aa81fd567496a35bef2566c1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7697917
Commit-Queue: Thomas Nguyen tungnh@chromium.org
Reviewed-by: Ravjit Uppal ravjit@chromium.org
Cr-Commit-Position: refs/heads/main@{#1604741}

merge_pr_58739

Add tentative scroll-state(stuck) for snapshot timing after scroll

Per HTML spec PR[1], run snapshot post-layout state steps is invoked
after layout for each iteration in the resizeObserver loop. Add a
scroll-state() container query test that makes sure a scroll after the
resizeObserver loop does not take effect until after the style/layout
update in the next resizeObserver loop.

[1] whatwg/html#11613

Bug: 384523570

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