Closed Bug 1598794 Opened 5 years ago Closed 4 years ago

[wpt-sync] Sync PR 20413 - Only enqueue at most one scroll event per frame.

Categories

(Core :: DOM: Core & HTML, 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 20413 into mozilla-central (this bug is closed when the sync is complete).

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

Chris Harrelson <chrishtr@chromium.org> wrote:

Only enqueue at most one scroll event per frame.

It doesn't seem to make sense to do so for forced layouts.
This causes extra CPU load, and can cause thrashing issues like
in the referenced bug.

There is no spec that requires the current behavior as far as I can
tell. The CSSOM spec calls out that it should fire "when the viewport
or element is scrolled" [1]

[1] https://drafts.csswg.org/cssom-view/#eventdef-document-scroll

Bug: 988991

Change-Id: I4e4ebcf2c5bcba8111d73ebd0b2b8a037034caaa
Reviewed-on: https://chromium-review.googlesource.com/1928243
WPT-Export-Revision: 63b9d874cfe598d533888844453268c0fd54de04

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

GitHub CI Results

wpt.fyi PR Results Base Results

Ran 1 tests and 1 subtests

Firefox

OK : 1
FAIL: 1

Chrome

OK : 1
PASS: 1

Safari

OK : 1
PASS: 1

Firefox-only failures

/html/interaction/focus/the-autofocus-attribute/update-the-rendering.html
"Flush autofocus candidates" should be happen before a scroll event and animation frame callbacks: Firefox: FAIL

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/015d75b07dd8
[wpt PR 20413] - Don't enqueue a scroll event for clamping or anchoring scrolls if not changed., a=testonly
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla73
You need to log in before you can comment on or make changes to this bug.