Steps to Reproduce:
1) Visit the following link on WebKit Nightly, Safari 5 or 6:
2) Quickly seek to a point *ahead* of the buffer
Video freezes, sometimes the whole buffer bar disappears and video playback can't be resumed. Other times the buffer bar doesn't disappear but it's frozen, playhead starts to advance for a couple of seconds and then it starts "looping", but in any case video playback is corrupted.
Video starts loading from the seeked point and playback is resumed automatically, this can be seen by simply changing https:// to http:// in the URL above.
On the one hand this is probably something Amazon should fix, because if the same video is hosted on another server/CDN (with a different SSL certificate) the issue can't be reproduced, but on the other hand this works fine on other browsers (Chrome, IE9, and also with a Flash player), so there is probably an issue to fix in Safari too.
> 1) Visit the following link on WebKit Nightly, Safari 5 or 6:
To clarify, are you saying that there is a regression aspect here?
Using Safari 5.1.7, I'm seeing some badness, and some weird behavior, like non-contiguous buffer display in progress track.
> To clarify, are you saying that there is a regression aspect here?
I actually tested this on a very old iBook G4 with Tiger and Safari 4.1.3, and I can't reproduce the issue.
So there might be a regression aspect here.
Interesting fact: if I open the source via "Open Location..." in QuickTime Player 10 (on my MacBook Pro running Lion) I can observe the same bug, while if I load it in QuickTime Player 7 (which I've also installed on my MacBook) it works correctly. This seems to explain why there's no issue on Safari 4 on the old iBook G4 (PPC/Tiger) where HTML5 Video - I suppose - is "powered by QuickTime 7" (but correct me if I'm wrong).
Is there any news about the status of this issue? I can confirm it (with a screencast if need be).
Would it be possible that at least someone mark it as confirmed so that it might be addressed in a (hopefully) near future?
Thanks very much in advance.
This seems to be fixed now. I'm not able to reproduce the problem anymore (Safari 6.0.2).
I don't know if you changed something in WebKit or if Amazon changed something on their side... but this is good news.