[Webkit-unassigned] [Bug 178120] Audio autoplay restrictions favor abusive content

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Oct 16 16:03:29 PDT 2017


--- Comment #4 from Jer Noble <jer.noble at apple.com> ---
(In reply to Ashley Gullen from comment #3)
> So if we have a game with 20 audio tracks, are you suggesting that we play()
> 20 <audio> elements in the first touch, and then assign a src later on?

Are you going to play 20 tracks simultaneously? Then yes. Otherwise, only do this for as many tracks will play at once.  Usually games have one BGA track playing at a time, and a number of more dynamic audio effects. So I would expect the number of audio elements you need to be in the low single digits.

> Isn't this kind of a bizarre workaround? Why not just allow play() at any
> time after the first touch? I don't understand why that's not the case -
> what are you protecting against?

Just because I hit the space bar to scroll doesn't mean a website should be allowed to blare audio-enabled ads at me.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20171016/7028e28e/attachment.html>

More information about the webkit-unassigned mailing list