Disable omnibox autocomplete for classes of queries

[Eric Burnett]

Hi everyone,

Is there any way to disable omnibox autocomplete for classes of
traffic? Specifically, I'd like it disabled for 1) anything that
parses as math, and 2) multi-word phrases. Suggestions in the drop-
down below are fine and welcome, but for these kinds of queries having
anything injected into the omnibox directly causes more mistakes than
it usefully helps with.

As a trivial example, typing '2' '/' '1' <return> results in the
browser searching for '2/10 would not'. '6' '/' '4' <return> results
in '6/49' being searched for, which is a math expression _with the
wrong value_. I have also seen cases where longer expressions will
have something tacked on at the end, resulting in chrome poisoning the
results of a math expression in ways that could potentially go
unnoticed.

For multi-word phrases, I just want it disabled because it's more
often wrong than not. Math expressions are my true pain point :).

Any chance this can be configured by modifying the search provider
string, or should I be filing a bug?

Thanks,
Eric

[Sreeram Ramachandran]

This is very likely because you got opted into an Instant field trial that provides these suggestions into the omnibox. You can opt out of this field trial (and all other forms of Instant) by passing --instant-field-trial=disabled on the command line. Then, you'll get drop down suggestions as before, but stuff will only get inline autocompleted into the omnibox if they match something in your history.

[Evans Turner (Work)]

...or, maybe, he should remain part of the trial and give feedback
about the problem it causes.

-Evans