The web page loaded is not displayed in most visited tiles of next new tab page. |
|||||
Issue descriptionApp Version: 61.0.3163.46 iOS Version: 10.3.3. 9.3.5, 11.0.0 beta 5 Device: iPhone and iPad URL: cnn.com Precondition: Install chrome and don’t sign in to chrome Steps to reproduce: 1. Launch chrome 2. Load any webpage (eg: cnn.com) 3. Once the page is loaded wait for few seconds/minute 4. Open a new tab page 5. Open another new tab page Observed results: At step 4: The most visited tile will not display At step 5: The most visited tile will display Note: It is also noticed that this issue is not happening for the very first webpage that is marked to most visited Expected results: The most visited tile should be displayed Number of times you were able to reproduce: 5/5 Bug reproducible after clean install: Yes Bug reproducible after clearing cache and cookies: Yes Bug reproducible on Chrome Mobile on Android: Not tested Bug reproducible on Safari/Firefox: Firefox: NA, Safari: NA Bug reproducible on current stable build (App Version, iOS Version): Yes on M60 Bug reproducible on the current beta channel build (App Version, iOS Version): Yes on M61 Link to video/image: https://drive.google.com/a/google.com/file/d/0B8Cek8RsDbF8ZFNkZ3dkMEtvNTA/view?usp=sharing
,
Aug 14 2017
,
Aug 17 2017
treib@: is it something expected from the Most Visited algorithm?
,
Aug 17 2017
Yeah, I think this is expected: Opening an NTP triggers a refresh of Most Likely, but it's async and we don't wait for it before populating the NTP. And then after it's populated, we don't want to change it while the user is looking at it. mastiz/fhorschig to confirm, but I believe this is WAI.
,
Aug 17 2017
That is true. There is no timing guarantee for suggestions (apart from not refreshing while user-facing). BTW: TopSites are a little bit faster. So after FR, currently visited pages appear very quickly but are not as sophisticated. As soon as we have MostLikely, the suggestions will update later.
,
Aug 17 2017
Thanks! Closing this as WAI. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mvanouwe...@chromium.org
, Aug 14 2017