On: Chrome will aggressively throttle background tabs

[__jal]

Bingo.

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.

[sirclueless → __jal]

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.

[chrissnell → sirclueless]

Just wait until background junk audio is included in a framework. We'll never be rid of it.

[wapz → chrissnell]

I already stopped visiting sites that had background audio autoplay. I don't think sites will get more traffic if they pick that up.

[ErikBjare → chrissnell]

I think you'll have to wait a long time. I doubt it'll ever happen.

[Piskvorrr → ErikBjare]

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."

[mdwrigh2 → __jal]

Note that you can always mute a tab in Chrome, which I suspect would remove the exemption as well.

[ErikBjare → mdwrigh2]

I wouldn't be so sure. I'd be interested in a definitive answer.

[altimin → ErikBjare]

Yes, muting a page means that this page is throttled again.