W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2015

Re: [whatwg] preload="metadata" elements don't necessarily fire "canplay"

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 7 Jul 2015 00:19:30 +1200
Message-ID: <CAOp6jLY66FA3KvDQ0nG2_DgJxQ0eJZjCbQcYuEKd971Lg3Bodw@mail.gmail.com>
To: Philip J├Ągenstedt <philipj@opera.com>
Cc: WHATWG <whatwg@whatwg.org>, Andrew Scherkus <scherkus@chromium.org>
On Mon, Jul 6, 2015 at 11:17 PM, Philip J├Ągenstedt <philipj@opera.com>

> On Wed, Jun 10, 2015 at 6:53 AM, Robert O'Callahan <robert@ocallahan.org>
> wrote:
> > In Gecko, <video preload="metadata"> doesn't fire "canplay". This is
> > allowed (encouraged, even) by the spec, since we can efficiently satisfy
> > preload="metadata" by stopping decoding after one frame, and if we only
> > decode one frame then readyState will not advance beyond
> > However, this may be counterintuitive for Web developers. Also, Chrome
> > fires "canplay" in this situation (although that's probably part of the
> > "Chrome fires canplay and canplaythrough willy-nilly" bug). Anyone else
> > have an opinion on this?
> Are you having site compat problems related to this?

There's https://bugzilla.mozilla.org/show_bug.cgi?id=1165203 (the same bug
as in the other thread), thought that involves load() as well. I don't know
of any sites where this causes problems in the absence of load(), though I
wouldn't be surprised if they exist. I think it would be a good idea to
align browser behaviors or the spec.

lbir ye,ea yer.tnietoehr  rdn rdsme,anea lurpr  edna e hnysnenh hhe uresyf
selthor  stor  edna  siewaoeodm  or v sstvr  esBa  kbvted,t
o l euetiuruewFa  kbn e hnystoivateweh uresyf tulsa rehr  rdm  or rnea
.a war hsrer holsa rodvted,t  nenh hneireseoouot.tniesiewaoeivatewt sstvr
Received on Monday, 6 July 2015 12:19:56 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:33 UTC