Re:Chrome will aggressively throttle background tabs
by sirclueless on Tuesday January 24, 2017 @04:27PM
(#13475671)
The audio thing works because there is an obvious icon in the tab bar that shows the source of audio, so if developers use it in an annoying way the user can easily respond appropriately.
Re:Chrome will aggressively throttle background tabs
by chrissnell on Tuesday January 24, 2017 @08:16PM
(#13477543)
Just wait until background junk audio is included in a framework. We'll never be rid of it.
Re:Chrome will aggressively throttle background tabs
by wapz on Wednesday January 25, 2017 @02:54AM
(#13479585)
I already stopped visiting sites that had background audio autoplay. I don't think sites will get more traffic if they pick that up.
Re:Chrome will aggressively throttle background tabs
by ErikBjare on Wednesday January 25, 2017 @02:58AM
(#13479598)
I think you'll have to wait a long time. I doubt it'll ever happen.
Re:Chrome will aggressively throttle background tabs
by Piskvorrr on Wednesday January 25, 2017 @07:51AM
(#13480965)
There is now an incentive to do this, so it will happen. Same as "with popup blockers everywhere, popups are now replaced with HTML5 above-content layers."
Re:Chrome will aggressively throttle background tabs
by mdwrigh2 on Tuesday January 24, 2017 @04:18PM
(#13475578)
Note that you can always mute a tab in Chrome, which I suspect would remove the exemption as well.
The user ultimately needs to retain control. And I'm especially interested in the exception for audio - that really should be user-controllable, otherwise it just encourages annoying page authors to be even more annoying.