New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 514656 link

Starred by 7 users

Issue metadata

Status: Fixed
Owner:
Closed: Sep 2015
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Launch-OWP
Launch-Accessibility: ----
Launch-Exp-Leadership: ----
Launch-Leadership: ----
Launch-Legal: ----
Launch-M-Approved: ----
Launch-M-Target: ----
Launch-Privacy: ----
Launch-Security: ----
Launch-Test: ----
Launch-UI: ----
Rollout-Type: ----



Sign in to add a comment

Launch requestIdleCallback

Project Member Reported by rmcilroy@chromium.org, Jul 28 2015

Issue description

Change description:
An API which allows posting of tasks which are schedule during periods when the browser is idle, and are passed a deadline when called which is calculated based on how long the browser expects to remain idle. This enables developers to perform background work on the main event loop, without impact latency-critical events such as animation and input response.

Changes to API surface:
- window.requestIdleCallback
- IdleDeadline object

Editors Draft Spec: https://w3c.github.io/requestidlecallback/

Support in other browsers:
Internet Explorer: Mixed public signals
Firefox: public support
Safari: no public signals
 
Implementation tracking bug: https://code.google.com/p/chromium/issues/detail?id=514651
Labels: -Hotlist-Scheduling Cr-Blink-Scheduler
Labels: -Cr-Blink-Scheduler Cr-Blink-Scheduling
Labels: -OWP-Standards-UnofficialSpec OWP-Standards-OfficialSpec m-47
Upgrading to official standard (working draft) and setting target milestone for m47.
Status: Fixed
Shipped!

Sign in to add a comment