[blink-dev] Re: Intent to Experiment: Increased max nesting level for setTimeout(0)

The change to the nesting level at which 4ms clamping kicks in (MaxUnthrottledTimeoutNestingLevel) never shipped, because Speedometer 2.1 is not affected by it like Speedometer 2.0 was. However, WebKit did implement this change: https://sourcegraph.com/github.com/WebKit/WebKit/-/commit/786e3e0b

Re: [blink-dev] Intent to Ship: Quick intensive timer throttling of loaded background pages

Hi blink-dev@! We experimented with the "Intensive Wake Up Throttling of Javascript Timers after 1 minute in Background" feature on Stable 1%. With 7 days of ramped up data, we observe small but statistically significant changes to CPU usage. In addition to these savings, this feature encourage

Re: [blink-dev] Intent to Ship: Quick intensive timer throttling of loaded background pages

population set, to >>>> get more meaningful results. >>>> >>>> In terms of the Blink process though, I'm not 100% sure what we want to >>>> do here, given that this is an intent to ship. Maybe best to send an intent >>>> to experiment

[blink-dev] Re: Intent to Prototype: Conservative page freezing on desktop

On Friday, June 2, 2023 at 1:02:39 PM UTC-4 Michaela Merz wrote: Thank you Francois. Here's an experience I'd like to share with you. I was watching and listening to a training presentation yesterday and was asked to look something up. So I opened a new tab to start looking it up. But the pre

[blink-dev] Re: Ready for Trial: Quick intensive timer throttling of loaded background pages

+Scott Haseley as an expert in this field. We would like to start experimenting with this intervention on 1% Stable very soon. We've been experimenting on 50% of Beta for almost 2 months. The results are encouraging and we aren't aware of negative Web developer feedback. Do we need your LGTM to p

Re: [blink-dev] Re: Ready for Trial: Quick intensive timer throttling of loaded background pages

for the experience you gather in this > experiment to fold back into the spec as an "Implementation Consideration" > that might help other implementers determine how to use the flexibility the > spec provides. > > -mike > > > On Fri, Aug 5, 2022 at 9:24 PM 'François Dor

Re: [blink-dev] Re: Ready for Trial: Quick intensive timer throttling of loaded background pages

al for the experience you gather in this >> experiment to fold back into the spec as an "Implementation Consideration" >> that might help other implementers determine how to use the flexibility the >> spec provides. >> >> -mike >> >> >> On Fr

Re: [blink-dev] Re: Ready for Trial: Quick intensive timer throttling of loaded background pages

isible experiment >>>>>> and a pure expression of user agent preference regarding flexibility >>>>>> explicitly carved out in a standard. >>>>>> >>>>>> Rather than debating the feature's philosophical state, I'd simply >

Re: [blink-dev] Intent to Ship: Freezing on Energy Saver

On Friday, November 29, 2024 at 3:13:39 PM UTC-5 Rick Byers wrote: tl;dr: Just one remaining question about providing a developer opt-out (like a deprecation trial). On Fri, Nov 29, 2024 at 12:25 PM Francois Pierre Doray wrote: Hi Rick, Thanks for raising your concerns regarding troublesho

Re: [blink-dev] Intent to Ship: Freezing on Energy Saver

Update: The feature is now enabled for 1% of Chrome 133 stable users (for these users, it only has an effect if Energy Saver is active and there are eligible CPU-intensive background tabs). This blog post provides details for Web deve

Re: [blink-dev] Intent to Ship: Freezing on Energy Saver

Hi everyone, Thanks for the feedback. Here are my responses: 1. An origin trial will allow Web developers to opt out of freezing. In addition to provide a quick way to prevent breakages, it will help us identify background use cases that might need dedicated APIs for support. 2. A blog post do

Re: [blink-dev] FYI: Frame rate throttling when no frames are produced

Hi, We will proceed with the Stable 1% experiment for this intervention. Rationale: - - The MotionMark regression is well understood. I discussed with +Camillo Bruni and we concluded that it isn't a blocker for measuring the impact of this intervention on Stable 1%. Howe