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

Issue 651420 link

Starred by 2 users
Status: Assigned
Owner:
dtrainor@chromium.org
Cc:
qin...@chromium.org
twelling...@chromium.org
asanka@chromium.org
█ dfalcant...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Download notification takes several seconds to appear on a slow network

Project Member Reported by mdw@chromium.org, Sep 29 2016 
Version: 55.0.2868.0
OS: Android NDE63N
Device: Sailfish

What steps will reproduce the problem?
(0) Be on a slow network.
(1) Visit https://www.ssyoutube.com/watch?v=OLuq3CKqky8
(3) Click the green 'Download' button.

What is the expected output?

I should immediately see some indication that a download has started, or will start soon.

What do you see instead?

It takes several seconds before anything appears; it looks like Chrome isn't doing anything or that perhaps I didn't correctly tap on the download button.

After a few seconds the 'Downloading' toast appears along with the Android notification.

I think we need to have an immediate visual indication that something is happening. I am assuming here that Chrome knows it is sending a request to some URL which is going to come back with some response; I don't know how the request-response flow on this particular page works, though.

Comment 1 by dah...@chromium.org, Sep 30 2016

Cc: asanka@chromium.org twelling...@chromium.org qin...@chromium.org dfalcant...@chromium.org
Owner: ----
Status: Untriaged (was: Assigned)
This repros for me. On 3G, the notification took about 5-10 seconds to appear. This creates the perception that the download didn't work and might cause users to create duplicates.

Comment 2 by asanka@chromium.org, Sep 30 2016 

Yeah. The downloads workflow currently starts when the server response is received. In general, the browser doesn't know a response should be downloaded until the response headers are available.

This particular site is different in that it uses an anchor with a download attribute. So the browser knows that there's going to be a download as soon as the renderer makes the DownloadUrl IPC. That is, assuming that the request will eventually proceed past the response headers phase.

One short term workaround would be to show a toast when an explicit download request is seen and then suppressing the toast that would've otherwise been displayed after the response headers are available.

Comment 3 by dtrainor@chromium.org, Jan 26 2017

Labels: -Pri-3 M-59 Pri-2
Owner: dtrainor@chromium.org
Status: Assigned (was: Untriaged)
Let's try to add some UMA stats to see how often the download attribute is present on links that led to a download.  Maybe it'd be worth adding the infrastructure to start up the notification on request for those.

Will look into a more comprehensive fix over the next few releases.
►

Sign in to add a comment