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

Issue 754115 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 2
Type: Bug



Sign in to add a comment

Out of the box MostLikely tiles don't match widget

Project Member Reported by jasonkliu@chromium.org, Aug 10 2017

Issue description

App Version (from "Chrome Settings > About Chrome"): 62.0.3180.0 canary
iOS Version: 10.2
Device: 5S

Steps to reproduce: 
Add the widgets

Observed behavior: 
My top sites on the NTP from a fresh install are:
1. FB
2. YT
3. Amazon
4. Wikipedia
5. ESPN
6. Yahoo
(reading left to right, top to bottom).

My top widget sites are:
1. FB
2. YT
3. Wikipedia
4. Amazon
5. Yahoo
6. ESPN
7. Instagram
8. Zillow

Expected behavior: 
Order should line up... but see additional comments

Frequency: Sometimes
<number of times you were able to reproduce> 

Additional comments: 
This bug seems to have corrected itself quickly but may be indicative that there is some syncing of initial populated tiles and predetermined tiles between NTP <> Widget?

 
IMG_0416.PNG
86.1 KB View Download
IMG_0417.PNG
608 KB View Download
Cc: gambard@chromium.org noyau@chromium.org
This is probably because there are "fall-back" tiles that are baked into the binary which we use if we're unable to fetch from server. I suspect that the widget got populated with the baked-in ones and the NTP with the server-side ones. 

Adding gambard@ and noyau@ who know about popular sites.
Status: Assigned (was: Unconfirmed)
You can go to chrome://ntp-tiles-internals on your phone to check the Most Visited tiles currently available.
If it only appears on new install and correct itself quickly, it is probably due to the difference between backed-in and downloaded most popular sites.

Comment 4 by lod@chromium.org, Oct 2 2017

Status: WontFix (was: Assigned)
I agree with gambard and mardini's analysis of the issue here. The baked in sites probably got saved to disk and hadn't yet been replaced by the downloaded ones when you opened the widget. Going to close this as won't fix; I don't see a reason this would occur other than when the NTP sites change and with just the right timing.

Sign in to add a comment