W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2012

Re: [whatwg] Firing canplaythrough when caches/buffers are full

From: Andrew Scherkus <scherkus@google.com>
Date: Wed, 30 May 2012 10:37:18 -0700
Message-ID: <CAG2o0ODjCgHv=rJELZ8ncTucMj+0bnyKznH6d+QsZksmEPMrng@mail.gmail.com>
To: Jer Noble <jer.noble@apple.com>
Cc: WHATWG <whatwg@whatwg.org>, robert@ocallahan.org
On Wed, May 30, 2012 at 9:47 AM, Jer Noble <jer.noble@apple.com> wrote:

>
> On May 27, 2012, at 5:51 PM, Robert O'Callahan <robert@ocallahan.org>
> wrote:
>
> > I propose fixing this by having the UA enter the HAVE_ENOUGH_DATA
> > readyState when the UA decides to suspend a download indefinitely and the
> > preload state is "Automatic" (or overriden by "autoplay" being set).
> >
> > We have checked in a patch to Gecko to do this. (Note that for a long
> time,
> > Gecko has triggered playback of autoplay elements when suspending due to
> > media buffers being full. The new change makes us enter HAVE_ENOUGH_DATA
> as
> > well.)
>
> For what it's worth, the Mac port of WebKit has this exact behavior: <
> http://trac.webkit.org/changeset/97944>.  It would be good to formalize
> this, however.
>

Chrome's canplaythrough logic (which admittedly needs a little work) has
similar behaviour. I agree it'd be good to formalize the behaviour.

Rob: when you say to suspend a download indefinitely would this coincide
with dropping the networkState to NETWORK_IDLE and subsequently firing a
suspend event?

Andrew
Received on Wednesday, 30 May 2012 17:37:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:08 GMT