[whatwg] Author control over media preloading/buffering
robert at ocallahan.org
Thu Feb 12 14:55:52 PST 2009
On Thu, Feb 12, 2009 at 10:13 PM, timeless <timeless at gmail.com> wrote:
> 2009/2/11 Robert O'Callahan <robert at ocallahan.org>:
> > So, how about adding an "autobuffer" attribute, which instructs the
> browser that the user
> > will probably play the video and as much data as possible should be
> > By default (when the attribute is not present) the browser would be
> expected to pause
> > the download after reaching HAVE_CURRENT_DATA if the media element is
> paused and not 'autoplay'.
> if i'm a mobile browser vendor (and I am), and if I expect to use
> Bluetooth to talk to a cell phone which has high bandwidth costs (and
> if you're using an n800/n810 tethered to a phone in Canada, this is
> true), then, i'm not sure I really want web pages to specify things
> quite like this.
Then you can have the browser ignore "autobuffer". Problem solved.
> bufferpriority="1", bufferpriority="2", which establish a sort and
> inform the browser which videos are most important, and the browser
> can then choose to collect as many of them as it feels comfortable
> collecting, possibly to the point that having played the highest
> priority, it proceeds to buffer the next highest priority video. If
> there are two things w/ bufferpriority="2", then the browser is free
> to treat them equally, but having already played one, it would then
> favor the other.
I don't really see a usecase for multiple priority levels. Do you have one?
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg