Closed Bug 786972 Opened 12 years ago Closed 12 years ago

Can't replay the same HTML5 youtube video by clicking on the progress bar after when it ends

Categories

(Core :: Audio/Video, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: ioana_damy, Unassigned)

References

Details

Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Firefox/17.0 (20120829042009)

STR:
1. Go to http://www.youtube.com/html5 and join the HTML5 trial.
2. Play a HTML5 video. Wait until the video ends and the Replay button gets displayed.
3. Click somewhere on the progress bar to go back to that moment of the video.

Actual Results:
The video player rewinds to the right moment of the video. The video stays paused and the video player button is also "Pause". The user can't get the video to play by using the Play/Pause button, nor by clicking the video. At this moment, the web page has to be refreshed to replay the video.

Expected Results:
The video player rewinds to the right moment of the video and the video plays from there - Google Chrome behavior. It could also rewind and let it on pause, but then the button should be "Play", not "Pause", and it should work fine.


Note:
This issue reproduces on all Firefox versions. It is most probably caused by a change in the website since I used youtube like this multiple times and it worked before. It does work on Chrome though, so we should see we if it can get fixed for us too.
Related to bug 777051?
(In reply to Matthew Gregan [:kinetik] from comment #1)
> Related to bug 777051?

Could be. The workaround from bug 777051 comment 0 works for this issue too. I don't get any errors/fired assertions though.
See Also: → 777051
This is caused by the patch for bug 778902, as I can reproduce on a normal page
with a <video> tag. It does work as comment 0 expects on release, because this
patch is only in Aurora and Nightly.

I mentioned in [1] that there will be a change in behavior (if the video ends,
the spec requires that switches to paused state). It is not clear to me if the
spec requires to start playback on a seek. I _guess_ point 10. of [2] implies
that we should restart playback after a seek in any case, but I don't feel that
it's right.

Something that we could do is to restart playback after a seek only if it is the
first seek after the playback has ended. We could also do nothing.

Fwiw, Chrome does not restart playback after a seek after the playback has ended
(our current behavior). Opera doesn't let me seek in the media at all.

I think this is also a problem on Youtube's side (like bug 778902), because
calling |play()| on the media element after a seek after the playback has ended
works perfectly fine. It is just the Youtube ui that is out of sync with the
<video> element (only on Firefox, not in Chrome, despite having the same
behavior).

[1]: https://bugzilla.mozilla.org/show_bug.cgi?id=778902#c3
[2]: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#dom-media-seek
(In reply to Paul ADENOT (:padenot) from comment #3)
> This is caused by the patch for bug 778902, as I can reproduce on a normal
> page
> with a <video> tag. It does work as comment 0 expects on release, because
> this
> patch is only in Aurora and Nightly.

Paul, it doesn't work as comment 0 expects on release. As I said in my note in comment 0, the issue reproduces on all versions. On release, Aurora, Beta, and Nightly, what is described under Actual Results reproduces. 

What isn't happening is the assertion, but that doesn't reproduce for me in Aurora or Nightly either.
Ah, I forgot Firefox 15 was released a couple days ago. I can reproduce on 15.

On the other hand, I can't reproduce on 14 anymore, for some reason.

Anyway, I _think_ this is a Youtube bug.
Does this happen on any other HTML5 video players with the latest Firefox Nightly?
(In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #6)
> Does this happen on any other HTML5 video players with the latest Firefox
> Nightly?

This issue doesn't reproduce anymore - tested on the 11/28 Nightly. Not sure what fixed it, but it works fine on all three main platforms.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.