4 ms·
I agree. I prefer it throttle everything but ask me if a page is important enough. A news site isn't important enough to ask for this but Slack is.
by codazoda 10y ago
I agree. I prefer it throttle everything but ask me if a page is important enough. A news site isn't important enough to ask for this but Slack is.
- nothrabannosir 10y agoTo 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 :)
- __jal 10y agoBingo. 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.
- mdwrigh2 10y agoNote that you can always mute a tab in Chrome, which I suspect would remove the exemption as well.
- sirclueless 10y agoThe 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 10y agoJust wait until background junk audio is included in a framework. We'll never be rid of it.
- wapz 10y agoI already stopped visiting sites that had background audio autoplay. I don't think sites will get more traffic if they pick that up.
- ErikBjare 10y agoI think you'll have to wait a long time. I doubt it'll ever happen.
- Piskvorrr 10y agoThere 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."
- ec109685 10y agoI don't want to switch to slack and wait several seconds before messages update. I'd rather the state be updated beforehand asynchronously.