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

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=178120

--- Comment #2 from Jer Noble <jer.noble at apple.com> ---
(In reply to Ashley Gullen from comment #0)
> Therefore beyond the first input, any abusive web content that wants to
> annoy the user can do so with the Web Audio API. However playback of Audio
> elements continues to be restricted.

Why aren't you just calling .load() or .play() on your long-playing <video> elements at the same time as starting your WebAudio context?  The restrictions are per element (or context). So you can .play() an empty <video> element, then later attach a src to it, and play unrestricted.

It seems to me that <video> elements and Web Audio contexts are actually /identically/ restricted.  Abusive authors could use the exact same tricks with <video> as they can with Web Audio.

-- 
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/82b6c5cd/attachment.html>