4 ms·
That's what happens when you let anybody and their friends run arbitrary code on the user's CPU. Javascript running by default was the original sin, and now the
by simias 6y ago
That's what happens when you let anybody and their friends run arbitrary code on the user's CPU. Javascript running by default was the original sin, and now there's no going back. IMO it ought to have been opt-in for the websites that really need it (i.e. web apps I actually want to use, not any random page I happen to stumble upon).
There's especially no going back for Google for whom it's very much a feature since they try to reimplement and replace the OS from within the browser.
- scrollaway 6y agoAnimated gifs are not arbitrary code and require no javascript. You're not really making a point that actually counters GP...
- boring_twenties 6y agoAnimated gifs are obviously trivial to block, so it doesn't seem worth even addressing that. The other half of the GP talks about rendering directly to canvas, using JavaScript...
- Zarel 6y agoThis comment was downvoted at the time I'm replying to it, but it's honestly the only reasonable objection here. The _only_ way to block autoplaying video is to block all animation, which means all of: - animated GIFs - nearly all JavaScript - CSS animation - partial rendering (showing the top part of a page before the entire page is done downloading) Everyone else calling for just blocking animated GIFs and canvas is just going to be hit by even more CPU and bandwidth intensive workarounds.