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

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

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 10 Jun 2015 16:53:30 +1200
Message-ID: <CAOp6jLY5rc9gK=QDEQaKyhnSf-1w012rrebh4fyF_7jF4Wo+Sw@mail.gmail.com>
To: WHATWG <whatwg@whatwg.org>
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 HAVE_CURRENT_DATA.
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?

oIo otoeololo oyooouo otohoaoto oaonoyooonoeo owohooo oioso oaonogoroyo
owoiotoho oao oboroootohoeoro oooro osoiosotoeoro owoiololo oboeo
osouobojoeocoto otooo ojouodogomoeonoto.o oAogoaoiono,o oaonoyooonoeo
osoaoyoso otooo oao oboroootohoeoro oooro osoiosotoeoro,o o‘oRoaocoao,o’o
oaonosowoeoroaoboloeo otooo otohoeo ocooouoroto.o oAonodo oaonoyooonoeo
osoaoyoso,o o‘oYooouo ofooooolo!o’o owoiololo oboeo oiono odoaonogoeoro
otohoeo ofoioroeo ooofo ohoeololo.
Received on Wednesday, 10 June 2015 04:54:17 UTC

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