Closed Bug 1582635 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 19173 - [IntersectionObserver] If necessary, schedule a frame after delay

Categories

(Core :: Layout, task, P4)

Product:
Core
Component:
Layout
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla71
Tracking Flags:
Tracking Status
firefox71 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Stefan Zager <szager@chromium.org> wrote:

[IntersectionObserver] If necessary, schedule a frame after delay

If the following sequence happens:

  • IntersectionObserver sends a notification
  • Layout is dirtied in a way that should generate a new notification
  • Lifecyce update runs
    • IntersectionObserver skips processing due to its 'delay' parameter

... then we need to guarantee that the IntersectionObserver will send
the necessary notification after the necessary delay. If animation
frames are being regularly generated, this won't be a problem, because
the observer will get a chance to run at the end of every lifecycle
update. But if the document goes dormant, and frames are not being
regularly generated, then we must force a lifecycle update after enough
time has passed, to give the observer a chance to run.

Change-Id: I74b63486e5c9b05c662f9e2e6e1c0b4baf00eba5

Reviewed-on: https://chromium-review.googlesource.com/1812798
WPT-Export-Revision: ab5fbf40654c3d93d0c2ba3e7c4057db77cee33f

Component: web-platform-tests → Layout
Product: Testing → Core
Ran 1 tests and 1 subtests OK : 1 FAIL : 1
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/64b838cbbfb4 [wpt PR 19173] - [IntersectionObserver] If necessary, schedule a frame after delay, a=testonly

https://hg.mozilla.org/mozilla-central/rev/64b838cbbfb4

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