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

Issue 750857 link

Starred by 1 user
Status: Fixed
Owner:
mastiz@chromium.org
Closed: Oct 2017
Cc:
mastiz@chromium.org
█ ramyan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug

Blocked on:
issue 751023


Sign in to add a comment

Duplicate MostLikely entry

Project Member Reported by kenjitoyama@chromium.org, Jul 31 2017 
Chrome Version: (copy from chrome://version)
OS: (e.g. Win7, OSX 10.9.5, etc...)

Mobile (Android)

What steps will reproduce the problem?
(1) Browse pages
(2) Open a new tab page (NTP)
(3) Two icons and landing pages are the same.

What is the expected result?

I was expecting to see only unique entries.

What happens instead?

I see duplicate entries.

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.


Screenshot of mostlikely.corp.google.com from a logged-in incognito session: https://screenshot.googleplex.com/MjhD4ax4F97

Output of chrome://ntp-tiles-internals/ from a logged-in incognito session:

Sources
TOP_SITES
enabled	no
SUGGESTIONS_SERVICE
enabled	no
POPULAR
enabled	no
WHITELIST
enabled	no
Update
Sites

Comment 1 by mastiz@chromium.org, Aug 1 2017

Blockedon: 751023

Comment 2 by mastiz@chromium.org, Aug 1 2017

Owner: mastiz@chromium.org
Status: Assigned (was: Untriaged)
Hi and thanks for reporting!

The underlying issue here is that news.google.com issues a client-side redirect that Chrome Sync doesn't represent well. I filed a bug for this and is blocking this one.

We do have ongoing experiments with workarounds that would fix your problem, but I think it's best to fix the underlying problem.

Comment 3 by mvanouwe...@chromium.org, Aug 2 2017

Labels: zine-triaged

Comment 4 by mastiz@chromium.org, Oct 24 2017

Status: Fixed (was: Assigned)
We recently rolled out a change that should've fixed this problem, or to be precise, worked it around. The underlying issue is still unresolved and linked as blocking bug for future reference, closing this now.
►

Sign in to add a comment