4 ms·
Autoplay with sound is a perfectly legitimate use case, but I agree with the status quo that it should not be allowed by default. In general, the "not an accep
by franga2000 5y ago
Autoplay with sound is a perfectly legitimate use case, but I agree with the status quo that it should not be allowed by default.
In general, the "not an acceptable use case" argument is almost always a harmful distraction - it angers people with legitimate use cases and that in turn gives fuel to those supporting it only for their own harmful use-cases. Call it what it is - a useful feature that happens to be commonly abused.
s/autoplay/cookies/g, etc.
- atoav 5y agoI thought about this a lot, but did not find a single case where I would like to have a website suddenly play audio without me specifically clicking "play" or "unmute" somewhere.
- franga2000 5y ago- media sites like YouTube (some people prefer that when they click on a new video, it actually starts playing) - notification sounds - playlists of any sort (music or video) Most of this can be worked around by prompting the user on load and then never reloading the page (SPA fetch-and-replace pattern), but even big sites screw this up (like YouTube, where the memory usage increases with every "fake reload"). Again, I wouldn't want just any site to do this unexpectedly, but the ones where I want those features should be able to do it.