Closed Bug 1830811 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 39796 - In smooth scroll test, use elapsed time to measure when scroll has ended

Categories

(Core :: DOM: CSS Object Model, task, P4)

Product:
Core
Component:
DOM: CSS Object Model
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
115 Branch
Tracking Flags:
Tracking Status
firefox115 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Stefan Zager <szager@chromium.org> wrote:

In smooth scroll test, use elapsed time to measure when scroll has ended

WPT must be designed to run on a wide variety of hardware and refresh
rates. Many of the tests have been retrofitted to accomodate test
hardware with very slow refresh rates, but some tests (like this one)
can fail when run on hardware with very fast refresh rates, because
500 animation frames may not be enough to reach the end of a scroll
animation.

With this change, we wait for 200 milliseconds and a minimum of 5
animation frames where the scroll offset doesn't change, with a
timeout after 8 seconds.

Bug: chromium:770028
Change-Id: I9c024cf48359dab384356285bba237fed1d57025
Reviewed-on: https://chromium-review.googlesource.com/4497336
WPT-Export-Revision: 193d810257821ee37c4735a3d34f1f2f3890c1e3

Component: web-platform-tests → DOM: CSS Object Model
Product: Testing → Core
Try push failed: decision task LYR2ub9-Tl67KYqWVE8M4g returned error
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9e005f478410 [wpt PR 39796] - In smooth scroll test, use elapsed time to measure when scroll has ended, a=testonly

https://hg.mozilla.org/mozilla-central/rev/9e005f478410

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox115: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 115 Branch
You need to log in before you can comment on or make changes to this bug.