Closed Bug 1596216 Opened 5 years ago Closed 4 years ago

[wpt-sync] Sync PR 20241 - Resnap containers on layout changes

Categories

(Core :: Layout: Scrolling and Overflow, task, P4)

task

Tracking

()

RESOLVED FIXED
mozilla73
Tracking Status
firefox73 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Kaan Alsan <alsan@google.com> wrote:

Resnap containers on layout changes

Per spec, snap containers now resnap to the previous snap target(s)
on relayouts; if the container was not previously snapped then it snaps
to the nearest snap point (includes on initial layout).

This patch only considers targets set on the main thread when
resnapping, as snap targets set on the impl thread are currently not
synced back to main; this behaviour will be implemented in a follow-up.

Bug:866127
Change-Id: I1442e0f464408fb5d9c49c5748a45aec0ed4d166
Reviewed-on: https://chromium-review.googlesource.com/1912906
WPT-Export-Revision: 082e133f11be11c91190e640fab8ff6817cfd643

Component: web-platform-tests → Layout: Scrolling and Overflow
Product: Testing → Core
PR 20241 applied with additional changes from upstream: 1800da473d395e5b11f9ef658e2cf4c8c3538561, 5b9f9a0d1be1e14cc222cfbc6069fc70cd5d2f8e
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/49c48e3a7816
[wpt PR 20241] - [css-scroll-snap] Resnap containers after layout changes, a=testonly
https://hg.mozilla.org/integration/autoland/rev/7bb90379494e
[wpt PR 20241] - Update wpt metadata, a=testonly
Test result changes from PR not available.
Status: REOPENED → RESOLVED
Closed: 5 years ago4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla73
You need to log in before you can comment on or make changes to this bug.