User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36 Steps to reproduce: Open http://agot.be/~lachambre/bug/20131205-1_bb_pl.webm and try seeking into it. Actual results: Most of the time Firefox stops playing and the video freeze rather than seeking. Sometimes it works fine so try a few times to reproduce. Seeking into the same file works fine using totem/GStreamer on my Fedora 19 so that's probably a Firefox issue. Expected results: Seeking works all the time.
Hmm. I can reproduce with 28.0a1 (2013-12-05) on Mac. It actually shows the keyframe immediately when I drag the playback position, but it doesn't actually play back. I left the tab open and it eventually did start playing ~30 minutes later. It looked in the network devtools panel like we'd made a range request off the end of the resource. Maybe we're not handling the failure correctly and it needs to time out?
Component: Untriaged → Video/Audio
Product: Firefox → Core
nope, not a bad range request. I was comparing the range offset to the returned Content-Length, which is of course for a 206 response not the length of the complete resource.
Component: Audio/Video → Audio/Video: Playback
Bryce - close this if you happen to fix it.
You need to log in before you can comment on or make changes to this bug.