Re: [whatwg] HTML video and IE, Safari, Firefox, Chrome
On Wed, Nov 5, 2014 at 3:46 AM, Martin Hoernig wrote:
> Thank you Rob!
>
> 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?
>>
> Yep.
>
I have a fix for that bug now. Thanks again.
>
> 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).
>>
> We have performed most of our tests in "high bandwidth" scenarios ("Since
> we know the network bit rate and the video bit rate, we can take the
> canplaythrough event as mandatory as well."). The only situation in which a
> difference exists is (4) reset, where playing has to be fired after canplay
> and right before canplaythrough. But, you are right, additional "low
> bandwidth" tests are a good addition. I'm thinking for example of a stall
> test ("The stall timeout is a user-agent defined length of time, which
> should be about three seconds.")
>
Low-bandwidth tests are particularly interesting to test because browser
developers tend to operate in high-bandwidth environments so don't pay
enough attention to low-bandwidth environments :-).
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 ofolo!o’o owoiololo oboeo oiono odoaonogoeoro
ooofo
otohoeo ofoioroeo ooofo ohoeololo.
Re: [whatwg] HTML video and IE, Safari, Firefox, Chrome
Thank you Rob!
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?
Yep.
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).
We have performed most of our tests in "high bandwidth" scenarios
("Since we know the network bit rate and the video bit rate, we can take
the canplaythrough event as mandatory as well."). The only situation in
which a difference exists is (4) reset, where playing has to be fired
after canplay and right before canplaythrough. But, you are right,
additional "low bandwidth" tests are a good addition. I'm thinking for
example of a stall test ("The stall timeout is a user-agent defined
length of time, which should be about three seconds.")
Martin
On 2014-11-03 22:54, Robert O'Callahan wrote:
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
Re: [whatwg] HTML video and IE, Safari, Firefox, Chrome
Thank you! We are interested in contributing and consider a integration, but we cannot communicate a timeframe for now (the next paper has to be published within the coming weeks...). On 2014-11-03 19:49, Domenic Denicola wrote: Impressive research, Martin! Would you and your team be willing to turn it into test cases for the web-platform-tests project [1]? That's usually a good way to get browsers to fix their bugs. Failing that, you might want to file bugs on the various browser bug trackers. [1]: https://github.com/w3c/web-platform-tests -Original Message- From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Martin Hoernig Sent: Monday, November 3, 2014 11:29 To: wha...@whatwg.org Subject: [whatwg] HTML video and IE, Safari, Firefox, Chrome Greetings, I would like to bring some strange behavior of current web browsers to your attention. We have checked the HTML video (mp4 containers) abilities of IE, Safari, Chrome and Firefox and noted some variations between the specification and implementations. Our attention was focused on the seeking abilities and event mechanisms. One example is a missing pause-event in IE after the video playback ends, but there is a lot more. We tried to create a powerful HTML video player and we had to realize that our main job was to create workarounds. Our full text is available at: http://www.ronpub.com/publications/ojwt/OJWT-v1i2n01_Hoernig.html Thanks and cheers, Martin
Re: [whatwg] HTML video and IE, Safari, Firefox, Chrome
On Tue, Nov 4, 2014 at 10:54 AM, Robert O'Callahan wrote: > 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? > I guess that's what you mean, since I can reproduce something like that locally. Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1093399. Thanks!!! 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 ofolo!o’o owoiololo oboeo oiono odoaonogoeoro ooofo otohoeo ofoioroeo ooofo ohoeololo.
Re: [whatwg] HTML video and IE, Safari, Firefox, Chrome
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 ofolo!o’o owoiololo oboeo oiono odoaonogoeoro ooofo otohoeo ofoioroeo ooofo ohoeololo.
Re: [whatwg] HTML video and IE, Safari, Firefox, Chrome
Impressive research, Martin! Would you and your team be willing to turn it into test cases for the web-platform-tests project [1]? That's usually a good way to get browsers to fix their bugs. Failing that, you might want to file bugs on the various browser bug trackers. [1]: https://github.com/w3c/web-platform-tests -Original Message- From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Martin Hoernig Sent: Monday, November 3, 2014 11:29 To: wha...@whatwg.org Subject: [whatwg] HTML video and IE, Safari, Firefox, Chrome Greetings, I would like to bring some strange behavior of current web browsers to your attention. We have checked the HTML video (mp4 containers) abilities of IE, Safari, Chrome and Firefox and noted some variations between the specification and implementations. Our attention was focused on the seeking abilities and event mechanisms. One example is a missing pause-event in IE after the video playback ends, but there is a lot more. We tried to create a powerful HTML video player and we had to realize that our main job was to create workarounds. Our full text is available at: http://www.ronpub.com/publications/ojwt/OJWT-v1i2n01_Hoernig.html Thanks and cheers, Martin
[whatwg] HTML video and IE, Safari, Firefox, Chrome
Greetings, I would like to bring some strange behavior of current web browsers to your attention. We have checked the HTML video (mp4 containers) abilities of IE, Safari, Chrome and Firefox and noted some variations between the specification and implementations. Our attention was focused on the seeking abilities and event mechanisms. One example is a missing pause-event in IE after the video playback ends, but there is a lot more. We tried to create a powerful HTML video player and we had to realize that our main job was to create workarounds. Our full text is available at: http://www.ronpub.com/publications/ojwt/OJWT-v1i2n01_Hoernig.html Thanks and cheers, Martin
