Hi, this is Alexander. I'm an engineer on Chromium team working on scheduling and on background tab throttling in particular. Firstly, I want to make clear that we are not shipping this in Chrome 56. We have enabled throttling as an experiment in beta channel to measure impact and collect feedback from web devs. We will aim to ship it in Chrome 57, subject to further feedback. In response to concerns voiced we will d…
Chrome will aggressively throttle background tabs
201–210 of 403 posts
Re: Chrome will aggressively throttle background tabs
#202Earlier quoted context omitted.
Yeah, I basically do the same thing, but that hardly ever requires 10 tabs for me. When that happens, finding tabs becomes especially harder once their width starts to shrink. As for read-later, I usually pull them into the bookmarks bar (top level, directly visible) to free up some space.
I use one-tab.com; works fantastically for me. Not a huge stretch to say it changed my life.
Re: Chrome will aggressively throttle background tabs
#203Hi, this is Alexander. I'm an engineer on Chromium team working on scheduling and on background tab throttling in particular. Firstly, I want to make clear that we are not shipping this in Chrome 56. We have enabled throttling as an experiment in beta channel to measure impact and collect feedback from web devs. We will aim to ship it in Chrome 57, subject to further feedback. In response to concerns voiced we will d…
Does this extend to SSE?
Re: Chrome will aggressively throttle background tabs
#204What are we supposed to do about stuff this? Like I wrote a video game https://play.basketball-gm.com/ that lets you open multiple tabs for viewing multiple screens even while simulation is occurring in another tab. But Chrome recently stopped running the simulation if it's in a background tab. Putting my simulation code in a Shared Worker would be nice, except Safari and IE will never support it and it seems likely…
As a developer you need to decide whether or not to support a browser, and if that browser doesn't provide the APIs you need then you should drop support for that feature in that browser. In this case, if Chrome is making a change that you can't or won't change your game for then the solution is to detect Chrome and display a "This game only works in a single tab in Chrome. Try Firefox!" message if a user opens it in…
Re: Chrome will aggressively throttle background tabs
#205 var doVisualUpdates = true;
document.addEventListener('visibilitychange', function(){
doVisualUpdates = !document.hidden;
});
Basically, you can use this to determine if your tab is running "in the background" and avoid redrawing/refreshing components to show updates that won't ever be seen.[1] https://twitter.com/cryptowat_ch/status/817502626896089090
Re: Chrome will aggressively throttle background tabs
#206Earlier quoted context omitted.
I meet many tab hoarders (always open a new one, never close any, ending up with hundrets), but just can't wrap my head around it! I hate having more than 6-7 simultaneously open because it gets increasingly harder to keep an overview of what you're doing. The same applies for IDE tabs or windows. Too much of them and finding the right one becomes increasingly hard, and losing the thread more likely.
Not if you use Tree Style Tabs. I've been using it for years and I have no idea how other people can efficiently browse the web without it.
Re: Chrome will aggressively throttle background tabs
#207Earlier quoted context omitted.
Yeah, I basically do the same thing, but that hardly ever requires 10 tabs for me. When that happens, finding tabs becomes especially harder once their width starts to shrink. As for read-later, I usually pull them into the bookmarks bar (top level, directly visible) to free up some space.
I use one-tab.com; works fantastically for me. Not a huge stretch to say it changed my life.
Re: Chrome will aggressively throttle background tabs
#208Earlier quoted context omitted.
Yeah, I basically do the same thing, but that hardly ever requires 10 tabs for me. When that happens, finding tabs becomes especially harder once their width starts to shrink. As for read-later, I usually pull them into the bookmarks bar (top level, directly visible) to free up some space.
I use one-tab.com; works fantastically for me. Not a huge stretch to say it changed my life.
Re: Chrome will aggressively throttle background tabs
#209Hi, this is Alexander. I'm an engineer on Chromium team working on scheduling and on background tab throttling in particular. Firstly, I want to make clear that we are not shipping this in Chrome 56. We have enabled throttling as an experiment in beta channel to measure impact and collect feedback from web devs. We will aim to ship it in Chrome 57, subject to further feedback. In response to concerns voiced we will d…
I'd recommend a different background color for the tab, except that I'd also like to see (sign in) profiles have distinct background colors to aid the user in keeping their profiles straight.
Re: Chrome will aggressively throttle background tabs
#210Hi, this is Alexander. I'm an engineer on Chromium team working on scheduling and on background tab throttling in particular. Firstly, I want to make clear that we are not shipping this in Chrome 56. We have enabled throttling as an experiment in beta channel to measure impact and collect feedback from web devs. We will aim to ship it in Chrome 57, subject to further feedback. In response to concerns voiced we will d…
I'd also appreciate it if nothing the website can do can override that. If I mute the audio, then it shouldn't be a signal, and you'll want to avoid using signals which the websites can trigger without user action.
Honestly, I'd prefer if there was some way to entirely suspend event processing on a tab, or at least timers.