502372 - Video plays after seek of ended video

Status: RESOLVED INVALID

(Core :: Audio/Video, defect)

Description

[Jaquez]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5 (.NET CLR 3.5.30729)

After a video is played until the end, if you seek to another point in the video, it begins playback again from that point but I would expect it to remain paused at that point.

Reproducible: Always

Steps to Reproduce:
1. Play video until the end
2. Seek to another point in the video
Actual Results:  
Video begins playback from seek location.

Expected Results:  
Video remains paused at seek location.

If, before seeking, you first pause the video (by right-click and selecting pause since the controls already indicate a paused state but the right-click menu does not as of this time due to bug 497603), it still plays upon seek, but if you seek a second time (before the end is reached again) it will then pause at the seek location as intended.  In other words:

Steps to Reproduce:
1. Play video until the end
2. Pause the video (most likely by right-clicking and selecting 'Pause')
3. Seek the video (video will play back as above)
4. Seek the video again before it reaches the end a second time
Actual Results:
Video remains paused at second seek location.

Expected Results:
Video remains paused at first seek location.

I haven't tested with the patch for bug 497603, but it would seem that it would eliminate step 2, still leaving 2 seeks required for pause to take effect.

Comment 1

[Matthew Gregan [:kinetik]]

The first described behaviour is correct according to the HTML5 spec.  At the end of playback, the video is in the state called "paused for user interaction":

> A media element is said to have paused for user interaction when its paused
> attribute is false, the readyState  attribute is either HAVE_FUTURE_DATA  or
> HAVE_ENOUGH_DATA  and the user agent has reached a point in the media resource
> where the user has to make a selection for the resource to continue.

> It is possible for a media element to have both ended playback and paused for
> user interaction at the same time.

I can't reproduce the second described behaviour, so I'll assume that was a bug we've since fixed.