New issue
Advanced search Search tips

Issue 873545 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
mard...@chromium.org
stkhapugin@chromium.org
emilyschechter@chromium.org
mpear...@chromium.org
martijnb@chromium.org
ios-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android , iOS
Pri: 2
Type: Feature


Participants' hotlists:
Omnibox-Bugs-on-mpearson-Radar

Show other hotlists

Other hotlists containing this issue:
Hotlist-2


Sign in to add a comment

Removing a site from most visited tile should remove it from zero-query suggest list

Project Member Reported by ghendel@chromium.org, Aug 13 
Remove a site from the most visited tiles listed on the NTP
Then open omnibox from any site and see that site is listed as one of the zero-query suggestions in iOS Chrome. 

Shouldn't this site be removed from the zero-query suggestions? Assigning to emilyschechter in case there was a product reasoning for the current behavior. Feel free to reassign it back if you think this is an iOS team call.

Comment 1 by mpear...@chromium.org, Aug 13 

I don't think there was a product decision.  Partially, blacklisting a most visited tiles does not delete the visits from the user's history, and thus doesn't affect what gets shown in zero suggest.

Some of this discrepancy is also related to bug 607111.

I think in the ideal world the two surfaces should act the same, but we're not there yet.  This discrepancy is in the NTP team's hands, as they say the ranking system the omnibox is using is actually better than the NTP page's suggestion order, so rather than have the omnibox zero suggest switch, they'd rather switch the NTP page to the better algorithm.  And they haven't yet.

Comment 2 by mpear...@chromium.org, Aug 15

Cc: emilyschechter@chromium.org
Components: -UI>Browser>Autofill UI>Browser>Omnibox>ZeroSuggest
Owner: ----
Status: Untriaged (was: Assigned)
Fixing component.

Marking as untriaged, so the next engineer can decide the next steps (consult 	emilyschechter@, mark as dup of bug 607111, or leave as a separate issue).  All are reasonable steps in my opinion.

Comment 3 by jdonnelly@chromium.org, Aug 16

Labels: -Type-Bug OS-Android Type-Feature
Status: Available (was: Untriaged)
Leaving this open as a feature request. I agree that the two should be the same and we've discussed this a few times previously so this is useful for tracking the idea.
►

Sign in to add a comment