[Youtube][HTML5] Video no longer works when seeking after an ad is played at the end

RESOLVED INVALID

Status

()

P1
normal
RESOLVED INVALID
4 years ago
4 years ago

People

(Reporter: FlorinMezei, Assigned: jya)

Tracking

(Blocks: 1 bug)

Trunk
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(firefox37- wontfix)

Details

(URL)

(Reporter)

Description

4 years ago
Reproducible with: 
- Firefox 37 RC2 - BuildID: 20150326190726
- latest Firefox 38 Aurora - BuildID: 20150327004016
- latest Firefox 39 Nightly - BuildID: 20150326030212

Reproducible on: Windows 7 x64 

Steps to reproduce:
1. Open Firefox with a fresh profile and go to: https://www.youtube.com/watch?v=mCB5uqAZNxQ.
2. Seek close to the end of the video and wait for it to finish.
3. When video ends an ad should be presented (if it's not presented then restart from step #1).
4. Skip the ad, and then seek inside the same video.

Expected results:
Video starts playing from where the user seeked.

Actual results:
Video does not start. The image is black, the seek bar does not move, and the pause button is not functional (clicking it does nothing).

Notes:
- the end result is similar to bug 1142992
- the key to getting this issue seems to be getting the ad at the end of the video - if the ad does not show then the issue does not appear (the URL used here always seems to generate an ad at the end of the video)
- about:media displays (in DevEdition):
https://www.youtube.com/watch?v=mCB5uqAZNxQ
	
	currentTime: 0
(Reporter)

Comment 1

4 years ago
Forgot to mention, but this is not a recent regression as I get the issue to show in Firefox 33.1.1 with HTML5 player set for YouTube (from https://www.youtube.com/html5).
(Reporter)

Comment 2

4 years ago
[Tracking Requested - why for this release]: I think this should be tracked together with bug 1142992, as it's potentially the same issue but triggered by different scenarios.
status-firefox37: --- → affected
status-firefox38: --- → affected
status-firefox39: --- → affected
tracking-firefox37: --- → ?
tracking-firefox38: --- → ?
tracking-firefox39: --- → ?
Tracking for 39 and 40. Though this isn't a recent regression it sounds like it is frequently reproducible and has a bad impact.
status-firefox40: --- → ?
tracking-firefox39: ? → +
tracking-firefox40: --- → +
I'm not tracking for 37 as we've shipped this issue for a few releases. I am tracking for 38 as we need to determine if this is a problem when playing with MSE or only HTML5 video.

ni Anthony
status-firefox37: affected → wontfix
tracking-firefox37: ? → -
tracking-firefox38: ? → +
Flags: needinfo?(ajones)

Updated

4 years ago
Priority: -- → P1
Assignee: nobody → jyavenard
Flags: needinfo?(ajones)
(Assignee)

Comment 5

4 years ago
Is that something you can only reproduce with that particular video?

This video is known to have a few encoding issues (segments aren't properly adjactents with 33ms gaps between them). I don't believe such videos are commonly seen on youtube.

This would lower how likely this issue is to occur.
Flags: needinfo?(florin.mezei)
(Assignee)

Comment 6

4 years ago
I never managed to get the ad at the end of the video.
I only ever sees the ad when the video starts. When I then skip the starting ad, seek close to the end, I see the screen showing that it will jump to the next video.

When you say seek next to the end of the video, what time precisely? that video is 10:48 long.

Do you seek 10s from the end, 20 ?
(Assignee)

Comment 7

4 years ago
This is a youtube bug.

When the ad plays at the end, the mediasource element is removed from the HTMLMediaElement. There's nothing left to play anymore.

I can reproduce the exact same behaviour in Chrome 39.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Flags: needinfo?(florin.mezei)
Resolution: --- → INVALID
(Assignee)

Comment 8

4 years ago
There is nothing to fix. So untracking...
status-firefox38: affected → ---
status-firefox39: affected → ---
status-firefox40: ? → ---
(Assignee)

Updated

4 years ago
tracking-firefox38: + → ---
tracking-firefox39: + → ---
tracking-firefox40: + → ---
You need to log in before you can comment on or make changes to this bug.