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

Issue 692118 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Audio can't change currentTime in local web server

Reported by ricardo....@gmail.com, Feb 14 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Download Archive.zip and unzip
2. Start webserver: php -S localhost:8000 (I've also tried with python SimpleHTTPServer)
3. Load page and try to jump to the middle of the song

What is the expected behavior?
The player should skip to the middle of the song.

What went wrong?
Sometimes it works, but most of the times it doesn't.
The player goes back to the beginning.

Did this work before? Yes This has been happening for at least one year.

Is it a problem with Flash or HTML5? HTML5

Does this work in other browsers? Yes

Chrome version: 56.0.2924.87  Channel: stable
OS Version: OS X 10.10.5
Flash Version: Shockwave Flash 24.0 r0

Contents of chrome://gpu:
(I removed this because the wizard wouldn't send my report due the comment being too long)



 
Seems like the wizard lost the attachment...
Archive.zip
2.1 MB Download
Cc: hongchan@chromium.org
Components: -Internals>Media Blink>Media
ricardo@

I am using the twisted server for the local development and your repro case works fine on my stable version of Chrome (m56) The light-weight web servers like SimpleHTTPServer or PhP server do not seem to work well with audio/video streaming. If you look at the log from the server, you might be able to see what's going on there.

From my experience working on Omnitone demo, SimpleHTTPServer always crashed after few attempts to fetch a 300MB video file on the fly. The twisted server solved the problem.

See if using the twisted server resolves this issue. If it persists, I will triage the issue to find a right Chromium engineer for you.
Even if the web server is part of the issue, I'm not having this issue in Firefox nor Safari.
Labels: Needs-Bisect Needs-Triage-M56
Cc: krajshree@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue in Mac 10.12.2 by using chrome reported version #56.0.2924.87 and latest canary #58.0.3012.0.

Steps followed to reproduce the issue are as follows:
-----------
1. Downloaded Archive.zip and unzipped it.
2. Started webserver: php -S localhost:8000 from terminal.
3. Loaded index.html page and tried to jump to the middle of the song.
4. Observed that player skipped to the middle of the song without any issues.

Attaching screen cast for reference

ricardo.cabello@ - Could you please check this issue on latest canary #58.0.3012.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!
692118.mp4
1.3 MB View Download
Components: -Blink>Media Internals>Media>Network
Unfortunately I can still reproduce with 58.0.3012.0.
Screenflick Movie 10.mp4
6.1 MB View Download
A friend of mine suggested https://www.npmjs.com/package/http-server and it seems to solve the problem.

I've attached the network panel for 3 different servers:

1. php -S localhost:8000
2. python -m SimpleHTTPServer
3. node http-server

Only with 3 Chrome can change audio.currentTime. Firefox can change it all of them.


php.png
127 KB View Download
python.png
133 KB View Download
node.png
139 KB View Download
Status: WontFix (was: Unconfirmed)
We don't allow seeking on 200 (no range-request support) type responses since seeks would have to download the whole resource. This is a bad user experience, so we prevent it for that reason, which hopefully helps developers avoid accidentally serving content in this way.
dalecurtis@

Dale, is there any document (e.g. spec or standard) that explains this policy? Any informative article/blog post would be useful for the future reference.
Not really, it's a fairly obvious result of serving media without range-requests though; but that assumes a certain base understanding of networking and media containers. The easiest thing we can probably say is always make sure your server supports range requests (206 responses). 

Sign in to add a comment