Closed Bug 1489671 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 12901 - Loosen timing expectation in IntersectionObserver WPTs

Categories

(Core :: Layout, enhancement, P4)

enhancement

Tracking

()

RESOLVED FIXED
mozilla64
Tracking Status
firefox64 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 12901 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/12901 Details from upstream follow. Ali Juma <ajuma@chromium.org> wrote: > Loosen timing expectation in IntersectionObserver WPTs > > IntersectionObserver WPTs expect that intersection observations are > delivered withing two step_timeouts of requestAnimationFrame. This > expectation holds in Blink, but doesn't necessarily hold in other engines. > In WebKit, requestAnimationFrame and layout are separate tasks, so it's > possible for the first step_timeout to fire in between rAF and layout, > leading to test flakiness. This CL makes tests wait for an additional > step_timeout to account for this. > > Change-Id: Iad80943db184bc4519ab323c3bd7cfac1256e175 > Reviewed-on: https://chromium-review.googlesource.com/1214176 > WPT-Export-Revision: 5756f6a53bc7f6ad87104c3f3ae855d8647070f3
Component: web-platform-tests → Layout
Product: Testing → Core
Ran 25 tests and 103 subtests OK : 25 PASS : 102 FAIL : 1
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/075ae9254379 [wpt PR 12901] - Loosen timing expectation in IntersectionObserver WPTs, a=testonly
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Pushed by archaeopteryx@coole-files.de: https://hg.mozilla.org/integration/mozilla-inbound/rev/56c514060216 [wpt PR 12901] - Loosen timing expectation in IntersectionObserver WPTs, a=testonly
Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Flags: needinfo?(james)
You need to log in before you can comment on or make changes to this bug.