"Don't throttle pinned tabs"
"Don't throttle pinned tabs"
You can see the discussion back and forth, here: https://groups.google.com/a/chromium.org/forum/#!topic/blink...
I can see where that will end up though. Everyone who's app was broken by this change will start playing zero volume audio, then the exception will be yanked back.
With the web poised to be the new platform for applications, there really needs to be some more thought put into how to accomplish that goal. The chrome devs already sunset some solutions in that space, like the HTML5 app cache. Now this. Nobody likes a constantly moving target.
What do I know though? I don't normally listen to audio on the web...
On the other hand, if they are using Pandora or similar, the end user probably wants the background tab playing and doing other work (showing current album cover art or whatever so it's there if you switch back to that tab).
I have an option set in FF's about:config that disables loading of my pinned tabs on startup, so I regularly keep 200-300 tabs open and only activate the ones I need.
Sometimes it takes weeks to clear my tabs because I barely see a performance hit from having so many open.
Extending that functionality to throttling seems natural to me.
https://chrome.google.com/webstore/detail/tab-pinner-keyboar...