Enter Intensive Wake Up throttling after 10 seconds if the page is fully loaded when it becomes hidden. Currently, wake ups from JS timers with a nesting level >= 5 are throttled to 1 per minute after the page
has spent 5 minutes in the background , which is very conservative and was chosen to allow a launch of Intensive Wake Up Throttling with minimal regression risk. We're now planning to reduce this timeout to 10 seconds if the page is fully loaded when hidden.
Not applicable. This feature changes the behavior of an existing API, while remaining spec-compliant ("Optionally, wait a further implementation-defined
length of time.")
Interoperability and Compatibility
Gecko: No signal
WebKit: No signal
Web developers: No signals
Other signals: The more conservative version of Intensive Wake Up Throttling shipped smoothly to 100% Stable more than 1 year ago. A few bugs were filed, but in all cases we've been able to propose workarounds which made apps more efficient (example).
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
No, this feature will only ship on desktop platforms.
Goals for experimentation
We plan to experiment on 1% Stable to confirm whether we observe the same memory and power improvements as in the lab and on lower channels. We will decide whether this intervention ships based on the experiment data.
Ongoing technical constraints
This is not a new Web Platform feature.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
This feature will only ship on desktop platforms. On Android, the system severely limits resource consumption from background renderers,
which makes this feature unnecessary.
Requires code in //chrome?
Link to entry on the Chrome Platform Status
This intent message was generated by Chrome