On Mon, Jan 4, 2010 at 8:15 AM, 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. I'm happy with this, too. I don't really see a need to rename the attribute, but if that's the consensus, I'm happy with it. I guess, leaving away the buffering attribute then just means to leave the decision to the browser, which would probably equate to "auto"? Cheers, Silvia.Received on Monday, 4 January 2010 02:50:43 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:06 UTC