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

On Sun, Jan 3, 2010 at 1:15 PM, Robert O'Callahan <robert@ocallahan.org> wrote:
> On Mon, Jan 4, 2010 at 12:37 AM, Philip Jägenstedt <philipj@opera.com>
> wrote:
>>
>> Replace it with a single multi-state attribute like "buffering" instead.
>> Values "none", "auto" (the default) and "full", or similar. Unless there's a
>> cleaner way to represent the semantics "this is (un)likely to be used"....
>
> I'm still unconvinced three states will actually be needed, but this
> proposal sounds OK to me. At least it's forwards-extensible if more than two
> states do turn out to be needed.

The advantage with a separate 'noautobuffer' attribute is that if it
turns out that no UA starts using heuristics when no buffering
attributes are specified, the noautobuffer attribute effectively
becomes a no-op, and can be removed in the future.

/ Jonas

Received on Sunday, 3 January 2010 21:39:49 UTC