News for hackers. Stuff that matters.
Re:Chrome will aggressively throttle background tabs by nothrabannosir on Tuesday January 24, 2017 @01:46PM (#13474234)
To be honest neither is slack. They've got push notifications through web service workers. What for would they need aggressive background activity?

I'm not saying this to be pedantic, just trying to nip this entitled vendor mentality in the bud. "We're important so give give give without asking." It's a bit what you see with permissions on mobile: the more famous a company is, the more brazen a permission policy they can get away with. It's only tangentially related actual functionality of the app.

This is not about you personally, by the way, but about vendors. You just shouldn't let them get away with it. Even if they're slack :)

Re:Chrome will aggressively throttle background tabs by __jal on Tuesday January 24, 2017 @02:32PM (#13474664)
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.

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.
Re:Chrome will aggressively throttle background tabs by ErikBjare on Wednesday January 25, 2017 @02:59AM (#13479608)
I wouldn't be so sure. I'd be interested in a definitive answer.
Re:Chrome will aggressively throttle background tabs by altimin on Wednesday January 25, 2017 @07:09AM (#13480742)
Yes, muting a page means that this page is throttled again.
Re:Chrome will aggressively throttle background tabs by ec109685 on Tuesday January 24, 2017 @11:44PM (#13478606)
I don't want to switch to slack and wait several seconds before messages update. I'd rather the state be updated beforehand asynchronously.