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

Issue 711070 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Choosing to "Download Later" a page suggested by Google Now always results in a blank page being downloaded

Project Member Reported by w...@chromium.org, Apr 12 2017

Issue description

Chrome Version: 57.0.2987.132
OS: Android Lollipop (Yotaphone2)

What steps will reproduce the problem?
(1) Set up Google Now, and Chrome, on the device, so that Google Now will include cards suggesting web pages to read.
(2) Take the handset offline.
(3) Open Google Now.
(4) Click on one of the proposed web pages.
(5) When prompted, choose to Download Later, since you're offline.
(6) Take the handset online (in my case, by joining a wi-fi network).
(7) Tap the "Download Complete" notification for the page.

What is the expected result?

Expect that when you tap the notification it opens Chrome, with an offline snapshot of the pages's content.

What happens instead?

The page is always blank, though it does seem that e.g. background colour is correctly downloaded.  This repros 100% reliably for all attempts to use Download Later from a Google Now suggestion.

chrome://offline-internals shows the size of the snapshots to be of the order of 1-5KB.

(Filing this since on my device this is a 100% repro, not an intermittent issue)
 

Comment 1 by w...@chromium.org, Apr 12 2017

Note that if I instead:
(1) Take handset offline.
(2) Type a URL into Chrome.
(3) Choose Download Later.
(4) Return to the home screen.
(5) Go online again.
(6) Tap the download complete notification.

then the page seems to have downloaded correctly; this seems specific to the Google Now route (possibly because that uses a frame rather than fully launching Chrome?)
Labels: -M-57
Owner: dim...@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by dim...@chromium.org, May 17 2017

Labels: -Pri-1 Pri-2
On Chrome build 60.0.3096.5 (current dev) and kitkat (4.4.4) I can not reproduce. I belive the version of Chrome may have something to do with that. Now is using CCT and in M57 our support for CCT was not complete...

Sign in to add a comment