New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 620185 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Videos no longer buffer to 100% when calling play() & pause()

Reported by mmcdonne...@gmail.com, Jun 15 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36

Example URL:
https://static.clickview.com.au/pages/ChromeLoadTest/ChromeLoadTest.html

Steps to reproduce the problem:
1. Opening the link in Chrome 49+ will only result in the video being partially buffered. Play and Pause events are invoked via JS.
2. Display the controls and select play and then pause. The video will actually be buffered completely (different behaviour vs. invoking via JS).    

What is the expected behavior?
The video should be buffered to 100%.

What went wrong?
In Chrome 48 and earlier, it was possible to force a video to be completely buffered by calling play and pause events in succession via JS. Since 49 this is no longer possible to achieve programmatically. Furthermore, when performing the same actions directly on a video element in the browser (ie. selecting play then pause) the video will infact be buffered completely (the expected behaviour).

Did this work before? Yes Chrome 48 and earlier.

Is it a problem with Flash or HTML5? HTML5

Does this work in other browsers? Yes 

Chrome version: 51.0.2704.84  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0
 
Cc: sande...@chromium.org
Owner: yini...@chromium.org
Status: Assigned (was: Unconfirmed)
this is a regression from prior build. I can track it NOT repro on 49.0.2568.0. I will find out the regressed build.
Status: WontFix (was: Assigned)
This is an intentional change to avoid downloading video content that is never watched (there are several common cases where this was triggered unintentionally). The buffering logic is now only triggered if the pause is inside a user gesture.

Applications that want full control of buffering should use MSE.

Sign in to add a comment