RE: [media] adding autoplay requirements to requirements doc

a) Yes, autoplay is a Boolean attribute, the absence of the flag indicates false, the idea though is that if it is present the UA is only allowed to actually start playing if the user has opted in to that behavior. That allows authors to rely on autoplay without having to add extra logic in the page. 
b) The original definition would apply, I did say "along the lines of", not that it was the complete solution.

-----Original Message-----
From: Maciej Stachowiak [mailto:mjs@apple.com] 
Sent: 20 April 2011 20:50
To: Sean Hayes
Cc: Eric Carlson; Philip Jägenstedt; public-html-a11y@w3.org
Subject: Re: [media] adding autoplay requirements to requirements doc



On Apr 20, 2011, at 10:10 AM, Sean Hayes wrote:

> That all makes a certain amount of sense; it would carry a little more weight if there were some language in the spec to the effect that autoplay is a request that the user agent can deny. For example,
> 
> Rather than defining autoplay as:
> " When present, the user agent (as described in the algorithm described herein) will automatically begin playback of the media resource as soon as it can do so without stopping "
> Instead define it along the lines of:
> " When present, the user agent (as described in the algorithm described herein) will; unless a user agent setting has been set indicating that immediate playback is allowed, move the media into a potentially playing but blocked state: http://www.whatwg.org/specs/web-apps/current-work/complete/video.html#blocked-media-element which is waiting for user interaction  http://www.whatwg.org/specs/web-apps/current-work/complete/video.html#paused-for-user-interaction "

This definition has some issues:

(a) Seems to presume that no-autoplay is the default setting; this will probably not be the case.
(b) Doesn't define what happens if immediate playback *is* allowed.

Regards,
Maciej

Received on Wednesday, 20 April 2011 20:12:32 UTC