Closed Bug 1757048 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 32974 - Don't report layout shift inside NG multicol containers.

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox100 fixed)

RESOLVED FIXED
100 Branch
Tracking Status
firefox100 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Morten Stenshorne <mstensho@chromium.org> wrote:

Don't report layout shift inside NG multicol containers.

We do it wrong for legacy multicol, and it's pretty hard to get the same
kind of wrong for LayoutNG. For now, just don't report any layout shift
at all inside a multicol container. Only report the before/after visual
rectangle of the multicol container itself.

Bug: 1178618
Change-Id: I616c5e2986dc4d55669d5f56c92a93a8a715b4f3
Reviewed-on: https://chromium-review.googlesource.com/3488389
WPT-Export-Revision: bdbde53b367aa3a5677a1636ed9d964e719edfd7

CI Results

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

Total 2 tests and 1 subtests

Status Summary

Firefox

OK : 2
FAIL: 2

Chrome

OK : 2
PASS: 1
FAIL: 1

Safari

OK : 2
FAIL: 2

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/layout-instability/multicol-000.html
Move balanced multicol container: FAIL (Chrome: PASS, Safari: FAIL)
/layout-instability/multicol-001.html
Move multicol container with overflow: FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d5ed5aa74424
[wpt PR 32974] - Don't report layout shift inside NG multicol containers., a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
You need to log in before you can comment on or make changes to this bug.