The potential compat risk of this seems significant, if it means that pages can start misbehaving or breaking after 10 seconds in the background, which seems common in workflows like logins or ecommerce, where you might be flipping back and forth between tabs to find passwords, confirm credit card transactions, etc.
Have there been any bug reports from the beta experiment yet? To increase confidence, can we run this experiment at 100% on beta, dev and canary for a few milestones before trying it on stable? Are there any other ways we can gain insight on the compat risk? On Tue, Nov 8, 2022 at 10:10 PM François Doray <fdo...@chromium.org> wrote: > Contact emailsjiahe.zh...@intel.com, fdo...@chromium.org > > Specification > https://html.spec.whatwg.org/multipage/timers-and-user-prompts.html > > Design docs > > https://docs.google.com/document/d/1WFyfKUUxqM7uKxKOGhLiOjyY6T7QRduVcuHN0f6vJkk/edit > > Summary > > 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 [1], 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. [1] > https://chromestatus.com/feature/4718288976216064 > > > Blink componentBlink>Scheduling > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EScheduling> > > TAG review statusNot applicable > > Risks > > 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 > <https://bugs.chromium.org/p/chromium/issues/detail?id=1186569#c16>). > > 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 not ship on desktop platforms. > > > > Debuggability > > 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)?No > > This feature will only ship on desktop platforms. On Android, the system > severely limits resource consumption in background renderers, which makes > this feature unnecessary. > > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ?Yes > > Flag namequick-intensive-throttling-after-loading > > Requires code in //chrome?False > > Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1324656 > > Estimated milestones > DevTrial on desktop > > Enabled by default on desktop 104 > > 109 > Anticipated spec changes > > Open questions about a feature may be a source of future web compat or > interop issues. Please list open issues (e.g. links to known github issues > in the project for the feature specification) whose resolution may > introduce web compat/interop risk (e.g., changing to naming or structure of > the API in a non-backward-compatible way). > > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5580139453743104 > > *Additional context* > > The 1% stable experiment shows that this feature reduces Chrome's CPU > usage and extends battery life, as desired. We plan to enable it by default > in M109. > > The 1% stable experiment is still ramping up, so we would like to keep > experimenting in M108, to get small confidence intervals for all our > metrics on all desktop platforms. > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGD3t5EGWuOZgo1k5XExKpnjsRM9nacEeFMyiXkEOwW%3DkOqRUQ%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGD3t5EGWuOZgo1k5XExKpnjsRM9nacEeFMyiXkEOwW%3DkOqRUQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYd-UXBxBusEeBsrzPv4RApZzBvKM4oTYOFeoN6JL3T-2A%40mail.gmail.com.
