- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 21 Apr 2011 04:33:52 +0000 (UTC)
- To: Sean Hayes <Sean.Hayes@microsoft.com>
- cc: Eric Carlson <eric.carlson@apple.com>, Philip Jägenstedt <philipj@opera.com>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>
On Wed, 20 Apr 2011, 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 "
That's not the definition, it's just a non-normative description. (You can
tell it's non-normative because there's no normative requirement -- none
of the works in that sentence are "must", "should", or "may".)
The actual requirement is in this section:
http://www.whatwg.org/specs/web-apps/current-work/complete/video.html#the-ready-states
...where it says:
If the autoplaying flag is true, and the paused attribute is true, and
the media element has an autoplay attribute specified, and the media
element's Document's browsing context did not have the sandboxed
automatic features browsing context flag set when the Document was
created, then the user agent may also set the paused attribute to
^^^
false, queue a task to fire a simple event named play, and queue a task
to fire a simple event named playing.
Specifically, note that it says "may", not "must". That's what makes it
optional for user agents.
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 21 April 2011 04:34:21 UTC