Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

when playing HTML5 video, VideoObj.currentTime=N fails

  • 6 Antworten
  • 2 haben dieses Problem
  • 3 Aufrufe
  • Letzte Antwort von LBPSlava

more options

Sample problem is at

http://132.236.21.62/collt/authoring/currentTime.htm

You will also see a description there, and here it is, too:

A base64-encoded webm video is embedded with the HTML5 VideoObj=document.createElement("video") command, with custom Play, Pause, and Rewind button. Play and Pause work fine. But after the video plays to the end, there is no way to play it again. The Rewind button uses the command VideoObj.currentTime=0.1. This works in FF 15 in Mac OSX as well as in Safari 5, Chrome 21 in Mac OS X and Safari 5, Chrome 21, and IE 9 in Windows. It fails with FF 15.0.1 in Windows. Happens every time. My Windows 7 is 64-bit.

Sample problem is at http://132.236.21.62/collt/authoring/currentTime.htm You will also see a description there, and here it is, too: A base64-encoded webm video is embedded with the HTML5 VideoObj=document.createElement("video") command, with custom Play, Pause, and Rewind button. Play and Pause work fine. But after the video plays to the end, there is no way to play it again. The Rewind button uses the command VideoObj.currentTime=0.1. This works in FF 15 in Mac OSX as well as in Safari 5, Chrome 21 in Mac OS X and Safari 5, Chrome 21, and IE 9 in Windows. It fails with FF 15.0.1 in Windows. Happens every time. My Windows 7 is 64-bit.

Alle Antworten (6)

more options

Confirmed. Looks like a regression.

You can try to file a bug report on this issue and attach a minimal test HTML file to the bug report.

more options

Thanks! I don't know how to file a bug report.

more options
more options

Thanks, bug submitted to Bugzilla as #795784.

more options

It is best to attach a (minimal) test page to the bug report.
That ensures that the test page keeps available even if you remove your web page in the future (the bug may not get fixed quickly).
You can make a shorter video and convert that to base64.

more options

Done! Bug #795784 submitted to Bugzilla now has an attachment, a single htm file, that shows the bug. Thanks.