3 ms·
I see a lot of suggestions to throttle or randomize the cache somehow, and none to stop JavaScript for background tabs. What are the reasons that disallowing ba
by dahart 8y ago
I see a lot of suggestions to throttle or randomize the cache somehow, and none to stop JavaScript for background tabs. What are the reasons that disallowing background JS might not be preferable? Doesn’t Safari do this by default? And I’m not sure but I imagine that even allowing a background timeslice every once in a while would allow for background notifications and connections while preventing timing attacks?
- MuppetMaster42 8y agoChrome throttles background JavaScript by default (disables requestAnimationFrame entirely, reduces allowed runtime to around 1% of real time, etc) [1]. However disabling it entirely would break a lot of use cases. Chat apps would stop working, push notifications would no longer come, web sockets would stop getting processed, feeds would not get refreshed. You'd break a lot of the web. Doing so would force more companies to push out their own separate apps... Which would probably be electron (and I know how much HN hates electron). [1] https://developers.google.com/web/updates/2017/03/background_tabs https://developers.google.com/web/updates/2017/03/background...