Closed Bug 1953277 Opened 11 days ago Closed 4 days ago

[wpt-sync] Sync PR 51271 - Reland "Fix bug where cc clip paths affected intersection behavior"

Categories

(Core :: CSS Parsing and Computation, task, P4)

task

Tracking

()

RESOLVED FIXED
138 Branch
Tracking Status
firefox138 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 51271 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/51271
Details from upstream follow.

Claire Chambers <clchambers@microsoft.com> wrote:

Reland "Fix bug where cc clip paths affected intersection behavior"

This reland includes a fix that prevents the clip rect from not
being properly offset. The previous iteration of this change
mistakenly included needs_mask_based_clip_path_ as a requirement
for offsetting the clip rect, leading to invalid behavior.

The test has been updated with a margin to prevent regressions
on this point.

This is a reland of commit a3e653cb68ffa703751f81c1756de5dc30ae82c2

Original change's description:

Fix bug where cc clip paths affected intersection behavior

This change fixes a bug where intersection observers would behave
differently depending on whether the feature is enabled or not. This
bug occurred because ClipPathClipper::LocalClipPathBoundingBox is
used both for painting and for computing intersections. This change
reverts ClipPathClipper::LocalClipPathBoundingBox back to its prior
behavior, and instead explicitly overrides usages when a cc clip path
animation is present.

Additionally, this change adds an extra flag to the clip paint
property so that it is dectectable in code whether there is a cc
clip path animation requiring an expanded rectangle. This allows
intersection observers to query the real 'precise' rectangle when
necessary, by means of a special flag.

A test is added for this case.

Bug: 394244260

Change-Id: I22024a0264366b055416eebefb91ffec8861e998
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6242433
Reviewed-by: Xianzhu Wang \<wangxianzhu@chromium.org>
Commit-Queue: Claire Chambers \<clchambers@microsoft.com>
Reviewed-by: Philip Rogers \<pdr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1427364}

Bug: 394244260
Change-Id: I9f7b33231b0a3b87fbf44a3726b7c593eaf6a20b

Reviewed-on: https://chromium-review.googlesource.com/6338287
WPT-Export-Revision: fd67aad29924dcec2f3393a7f8c222fc0b55519f

PR 51271 applied with additional changes from upstream: 1987fdaadb1afabd5d430f500a0e9200e8d933ac
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 1 subtests

Status Summary

Firefox

OK : 1
FAIL: 1

Chrome

OK : 1
FAIL: 1

Safari

OK : 1
FAIL: 1

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6efa26c2d27a [wpt PR 51271] - Reland "Fix bug where cc clip paths affected intersection behavior", a=testonly
Status: NEW → RESOLVED
Closed: 4 days ago
Resolution: --- → FIXED
Target Milestone: --- → 138 Branch
You need to log in before you can comment on or make changes to this bug.