Re:How I doubled the battery life on my Mac by closing one t...
by tluyben2 on Wednesday February 17, 2016 @10:39PM
(#11123549)
But why can you not choose to either keep tabs you are not currently in focus with (so you are looking at another tab than the 50 others you have open) fully running, running at some max % or freeze completely? The latter just freezing the process which will require unfreeze but as it is a user choice it depends on their browser behavior.
Re:How I doubled the battery life on my Mac by closing one t...
by Mithaldu on Wednesday February 17, 2016 @11:15PM
(#11123683)
I was commenting on doing such automatically. (Hard to implement.)
Doing it manually would be great, but then you run into Chrome's obsession with remaining simple and "slim", regardless of whether this happens to the detriment of users.
Re:How I doubled the battery life on my Mac by closing one t...
by Houshalter on Wednesday February 17, 2016 @06:50PM
(#11122548)
Well that's how it works on my computer currently. If you put a browser game in the background it will slow down massively. If you want it to keep working, you need to move it to it's own window. Tabs that are in their own window keep running at full speed.
That is a naive view on it. Javascript can be doing a LOT of things. It could be rotating a product carousel; or it could be running a browser game. In both cases that's something that can use a LOT of CPU, but in the latter case the user might want it to continue processing in the background. How is the browser supposed to differentiate this on its own?