[Bug 8731] Consider expanding buffering control for media elements


Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:

           What    |Removed                     |Added
                 CC|                            |Simetrical+w3cbug@gmail.com

--- Comment #2 from Aryeh Gregor <Simetrical+w3cbug@gmail.com>  2010-01-13 16:11:44 ---
As an added comment, I think the spec should encourage browsers to use
heuristics here if no attribute is specified.

(In reply to comment #0)
>   * preload=all (or preload=full?) - request to buffer as much as possible -
> same as current autobuffer attribute

The current autobuffer attribute doesn't actually say this is what should
happen, it's just Firefox happens to implement it this way.

>   * preload=playthrough - preload metadata plus however much of the media item
> seems enough to play through
> Not all agree that the fourth value is worthwhile.

Who said that?  As far as I can tell, the first one to suggest this value was
Boris Zbarsky on January 9.  There were only three posts in the thread after
that before you posted this bug, and all three implicitly endorsed the
playthrough value.

If anything, I think the "none" value is the most dubious -- authors who don't
read the spec might not realize it won't even fetch the duration, and will
assume it behaves like "metadata".  Usually you'd only require one or two extra
requests to get the metadata anyway, on par with an image or two, so it seems
unlikely to be very useful, but might be confusing.  (Especially if Range: N,-M
actually works on common servers, and/or X-Content-Duration or similar starts
being used with Theora.)

(Maybe you meant "first" instead of "fourth"?)

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 Wednesday, 13 January 2010 16:11:47 UTC