W3C home > Mailing lists > Public > public-html@w3.org > December 2009

Re: Public feedback on HTML5 video

From: Jeremy Keith <jeremy@adactio.com>
Date: Mon, 28 Dec 2009 12:22:11 -0700
Message-Id: <751562B1-8893-4919-9E2E-976DC3B83E86@adactio.com>
To: HTMLwg <public-html@w3.org>
Philip wrote:
>> The author should be able to communicate to the browser
>> - whether it should buffer or not (determining how much this would  
>> be is something best left to the browser manufacturer)
>
> autobuffer does this.

Not quite.

Autobuffer allows the author to specify when a file should be pre- 
buffered.
Autobuffer *does not* allow the author to specify when a file should  
*not* be pre-buffered.

I too interpreted the spec to mean "the absence of the autobuffer  
attribute indicates that the file should not be pre-buffered" (hence  
my comment on that Webkit bug a while back). However, when I raised  
this point in the IRC channel, I was told that I was misinterpreting  
the spec.

Some clarification in the spec would be good here.

Is the absence of the autobuffer attribute an explicit request not to  
pre-buffer?

Currently, the spec doesn't clearly answer that question. It only  
describes what happens when the autobuffer attribute is present; it  
doesn't describe what happens when the autobuffer attribute is not  
present.

Here is my suggestion for the updated text:

"The autobuffer attribute is a boolean attribute. Its presence hints  
to the user agent that the author believes that the media element will  
likely be used, even though the element does not have an autoplay  
attribute. Its absence hints to the user agent that the author  
believes that the media element might never be used."

This extra sentence ties the absence of the attribute to author  
intention: something that is currently missing.

-- 
Jeremy Keith

a d a c t i o

http://adactio.com/
Received on Monday, 28 December 2009 19:22:45 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:55 UTC