New issue
Advanced search Search tips

Issue 866188 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Jul 26
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Rich entities not showing on Win10

Project Member Reported by emilyschechter@chromium.org, Jul 20

Issue description

In Win10, we set chrome://flags/#upcoming-ui-features and *no other flags*, but cannot trigger rich entities.

However, when tested on Mac, set chrome://flags/#upcoming-ui-features and *no other flags*, we see rich entities.

Something is wrong with the flag setup for Views maybe?
 
I tried to repro this on Win10 as part of Omnibox sheriff, and I could not.

In other words, rich entities seem to be showing up on Windows Canary as expected.
I wonder if this is a timing issue.  I just ran Win10 Canary 70.0.3500.0 and reset ALL flags to default.  Entity suggestions do appear.
Status: Assigned (was: Untriaged)
Labels: Group-Omnibox
Entities are not enabled by chrome://flags/#upcoming-ui-features because they require an experimental config to trigger the behavior on the server. They *are* enabled 100% in Canary Dogfood, but only if you *don't* have any other omnibox chrome://flags enabled (#upcoming-ui-features is ok, though).

All that being said, I can't explain the difference between Win and Mac described in #1. It should work the same for either. Just to double-check, the Win10 machine was running Canary?
Hm this was ainslie's device, will ask him.
Status: WontFix (was: Assigned)
Confirmed that the device in question was a non-corp machine that that enabling chrome://flags/#omnibox-rich-entity-suggestions produced rich entities.

Per email discussion, closing this issue, as forcing rich entities with chrome://flags/#upcoming-ui-features would add additional complexity to the configs that I'd like to avoid.

Sign in to add a comment