W3C home > Mailing lists > Public > public-html@w3.org > January 2010

Re: Should <video> buffer control be tri-state?

From: Robert O'Callahan <robert@ocallahan.org>
Date: Sun, 3 Jan 2010 19:47:12 +1300
Message-ID: <11e306601001022247of87c149v8f43108ee0ab7c00@mail.gmail.com>
To: Maciej Stachowiak <mjs@apple.com>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Philip J├Ągenstedt <philipj@opera.com>, "Edward O'Connor" <hober0@gmail.com>, Jeremy Keith <jeremy@adactio.com>, HTMLwg <public-html@w3.org>
On Sun, Jan 3, 2010 at 5:42 PM, Maciej Stachowiak <mjs@apple.com> wrote:

> It would have no visible effect other than performance, and the difference
> would be much less in the typical test environment where the author has a
> very fast pipe to his or her deployment server.
>

The performance effect is very noticeable, and if your controls UI shows the
buffer state, it's quite obvious what's going on.

One problem with making 'autobuffer' tri-state is that autobuffer="off" (or
whatever) is actually going to enable buffering in user-agents that support
the current autobuffer spec (i.e., Firefox).

Rob
-- 
"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
53:5-6]
Received on Sunday, 3 January 2010 06:47:44 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:12 UTC