Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

FireFox 35 breaks video seeking?


After updating to FireFox 35, seeking/scrubbing no longer seems to work in jwplayer. Nothing happens at all when the video bar is clicked.

Our player uses quite a lot of jwplayer's more advanced scripting features, but we haven't as yet found the source of the problem. Seeking works correctly if we navigate directly to the MP4 file, so it's definitely related to jwplayer in some way.

You can see an example of our player at this address:
http://excelcentral.com/excel2013/essential/lessons/0101%20Start%20Excel%20and%20open%20a%20new%20blank%20workbook.html

We updated to the latest version of jwplayer this morning, but this does not seem to have solved the problem. Any guidance you can offer would be appreciated!

10 Community Answers

mikesmart

User  
0 rated :

A much simpler example with the same problems at:
http://excelcentral.com/jwplayer/test.html

jherrieven

User  
0 rated :

@mikesmart

What OS are you using? Your second example works fine for me on Win7/FF35.

The original example doesn't work because I visited too many times in my debug process and it now requires me to register!

James Herrieven

MisterNeutron

User  
0 rated :

For me, the problem shows up in FF35 both on Win7 and on OSX. No forward-seeking is possible. Not sure why. On my own videos it works properly, so I have to assume that it's an encoding problem of some sort.

MisterNeutron

User  
0 rated :

Almost certainly unrelated to this problem, your coding is an odd mix of XHTML and HTML5. Choose one!

jherrieven

User  
0 rated :

@MisterNeutron - Just to be clear, does the second example not work for you in Win7/FF35?

James

mikesmart

User  
0 rated :

It's interesting to note that the problem seems to be intermittent - seeking does seem to be possible on rare occasions with exactly the same code and video file.

We're putting this down to some kind of FireFox issue, since everything seemed to work fine before the update to version 35 and continues to work in Chrome and Internet Explorer.

MisterNeutron

User  
0 rated :

The second example (the simple embed) fails for me in FF35/Win7 - it plays, but seeking doesn't work. But if I pull up the same video in FF35, without invoking JW Player at all, it works just fine.

But here's where it gets interesting - I grabbed the video, did nothing to it (didn't re-encode), and put up a test page on my own domain. From there, it works just fine:

http://misterneutron.com/ExcelTest/ (I won't leave it up there for long)

Maybe the confused DOCTYPE on the original page really IS doing something weird? Or something server-side? Tough to sort out....

mikesmart

User  
0 rated :

After checking with Fiddler, I found that the only difference between our video handler's response and the server's 'standard' response was that we were returning a 200 response code if a range request was sent for the entire file.

It seems that Firefox 35 requires a 206 code to be sent in response to any range requests, even if they ask for the entire file. Switching from 200 to 206 seems to have solved the problem.

The funny thing is that we originally switched to 200 response codes because Chrome refused to work with a 206! The latest version of Chrome seems to have addressed this, though, so everything is working great on all browsers now.

Thanks a lot to everyone who looked into this for us.

MisterNeutron

User  
0 rated :

Wow, that's a really obscure issue! Thanks for posting back about it.

Ethan Feldman

JW Player Support Agent  
0 rated :

Very interesting, this is a very good catch.

This question has received the maximum number of answers.