Issue metadata
Sign in to add a comment
|
OWP Launch bug: Throttle timers in out-of-view frames |
||||||||||||||||||||||||||||||||||||||||
Issue descriptionChange description: As an intervention we want to limit the rate at which timers in out-of-view, cross-origin frames are able to fire. Until very recently it wasn't possible for script authors to easily determine whether their content was visible to the user or not. A common pattern therefore is to use a continuous setTimeout() loop for driving animations without considering visibility, which can be very costly for performance. Changes to API surface: - setTimeout(), setInterval() callbacks will be aligned to a 1 Hz cadence in cross-origin, out-of-view iframes. The same intervention is already done when a tab goes into the background. Links: Public standards discussion: https://github.com/WICG/interventions/issues/9 Support in other browsers: Edge: Public support (https://github.com/WICG/interventions/issues/9#issuecomment-228800016) Firefox: In development (https://bugzilla.mozilla.org/show_bug.cgi?id=1145439) Safari: Shipped in version 9 (https://bugs.webkit.org/show_bug.cgi?id=145465)
,
Jun 30 2016
Flipping most of the bits to N/A. Test: there is no need for manual testing so NA. Privacy and Security: are N/A given that the change (throttling a web platform feature on a visibility condition) has no implications for these areas. Flipping to OWP-Design-Yes based on the approvals we got on the intent to implement and ship thread: https://groups.google.com/a/chromium.org/d/msg/blink-dev/_Lhz8THHk2Q/f8j8E49rAgAJ I'll reach out to Legal and L-R to get the remaining approvals.
,
Jun 30 2016
Approved over email
,
Jun 30 2016
,
Apr 5 2017
|
|||||||||||||||||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||||||||||||||||
Comment 1 by kenjibaheux@chromium.org
, Jun 30 2016