Closed Bug 1735597 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 31215 - Do not use pixel snapped values for intersection observer target rect

Categories

(Core :: Layout, task, P4)

task

Tracking

()

RESOLVED FIXED
95 Branch
Tracking Status
firefox95 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Philip Rogers <pdr@chromium.org> wrote:

Do not use pixel snapped values for intersection observer target rect

This patch switches from using the pixel-snapped BorderBoundingBox to
the unsnapped PhysicalBorderBoxRect which fixes a bug where the
intersection ratio would be slightly off due to this snapping.

Bug: 1020466
Change-Id: Id8e1472c498b10b36b691fa87aaf606a438b70c1

Reviewed-on: https://chromium-review.googlesource.com/3219840
WPT-Export-Revision: 263c19e93be3cc36c0fee2dcbd46c2eeaeb21efd

Component: web-platform-tests → Layout
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
PASS: 1

Chrome

OK : 1
FAIL: 1

Safari

OK : 1
PASS: 1

Links

GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a5fbad092172 [wpt PR 31215] - Do not use pixel snapped values for intersection observer target rect, a=testonly
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 95 Branch
You need to log in before you can comment on or make changes to this bug.