- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Tue, 4 Nov 2014 10:54:00 +1300
- To: Martin Hoernig <hoernig@in.tum.de>
- Cc: WHATWG <whatwg@whatwg.org>
Thanks for the testing! Please file bugs against browsers where you feel they're not following the spec. I'm not sure what this means: > Firefox fires the canplaythrough event after buffering is completed or > halted instead of a bandwidth depending solution > Do you mean that even when the data is arriving at a very high rate, we don't fire canplaythrough until all the data is downloaded? You might want to test canplaythrough a bit more carefully; your tests didn't find http://code.google.com/p/chromium/issues/detail?id=73609 (canplaythrough is basically unimplemented in Chrome; Chrome fires it immediately after canplay in all circumstances, which causes problems for other browsers). Rob -- oIo otoeololo oyooouo otohoaoto oaonoyooonoeo owohooo oioso oaonogoroyo owoiotoho oao oboroootohoeoro oooro osoiosotoeoro owoiololo oboeo osouobojoeocoto otooo ojouodogomoeonoto.o oAogoaoiono,o oaonoyooonoeo owohooo osoaoyoso otooo oao oboroootohoeoro oooro osoiosotoeoro,o o‘oRoaocoao,o’o oioso oaonosowoeoroaoboloeo otooo otohoeo ocooouoroto.o oAonodo oaonoyooonoeo owohooo osoaoyoso,o o‘oYooouo ofooooolo!o’o owoiololo oboeo oiono odoaonogoeoro ooofo otohoeo ofoioroeo ooofo ohoeololo.
Received on Monday, 3 November 2014 21:54:27 UTC