[Bug 11602] define precisely how autoplay overried preload

http://www.w3.org/Bugs/Public/show_bug.cgi?id=11602

Philip Jägenstedt <philipj@opera.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |philipj@opera.com

--- Comment #1 from Philip Jägenstedt <philipj@opera.com> 2010-12-23 14:29:01 UTC ---
A spec note now says "Note: The autoplay attribute can override the preload
attribute (since if the media plays, it naturally has to buffer first,
regardless of the hint given by the preload attribute). Including both is not
an error, however."

It should be defined precisely how autoplay and preload interact, assuming that
the UA honors them both and they haven't been overridden by user preferences.

Specifically:

1. <video preload="none" autoplay>

This is a contradiction in terms. Should the video load at all? If it does, it
must load to at least canplaythrough, as that's what triggers autoplay. I'd
consider making this markup non-conforming, as clearly the author is confused.
Even so, the behavior must be defined.

2. <video preload="metadata" autoplay>

Same issue as above, except it's unclear if the UA should load up to
loadedmetadata or canplaythrough. Since metadata is the default preload state,
this behavior is very important. Using autoplay implies that one must load to
canplaythrough, so it's really a fourth internal state in addition to the 3
exposed preload states.

3. <video preload="metadata" oncanplaythrough="this.play()">

If adding the autoplay attribute influences the buffering behavior, should
attaching event handlers do the same?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 23 December 2010 14:29:03 UTC