Closed Bug 1594624 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 20141 - When performing subtree layout, perform scroll anchoring notifications on ancestors.

Categories

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

Product:
Core
Component:
Layout: Scrolling and Overflow
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla72
Tracking Flags:
Tracking Status
firefox72 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Chris Harrelson <chrishtr@chromium.org> wrote:

When performing subtree layout, perform scroll anchoring notifications on ancestors.

Previously, we would fail to call NotifyBeforeLayout for all such ancestors
that are scrollers, causing subtree layouts to completely fail to maintain
a scroll anchor for such ancestors.

Bug: 920289

Change-Id: I899634949739f5d4f3af1f282b598cbc4ef0e3e4

Reviewed-on: https://chromium-review.googlesource.com/1902767
WPT-Export-Revision: 958aef40d6c10fd4e5586682fd738bc869ac68eb

Component: web-platform-tests → Layout: Scrolling and Overflow
Product: Testing → Core
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f50cd1448a61 [wpt PR 20141] - When performing subtree layout, perform scroll anchoring notifications on ancestors., a=testonly https://hg.mozilla.org/integration/autoland/rev/c4759d9e9c34 [wpt PR 20141] - Update wpt metadata, a=testonly
Test result changes from PR not available.

https://hg.mozilla.org/mozilla-central/rev/f50cd1448a61
https://hg.mozilla.org/mozilla-central/rev/c4759d9e9c34

Status: REOPENED → RESOLVED
Closed: 6 years ago → 6 years ago
status-firefox72: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
You need to log in before you can comment on or make changes to this bug.