Merging into  issue 91378 .

pkasting@: Please reopen, if this should be keep stay open as a feature request.

Thanks.

Please consider re-opening this issue, pkasting@. Disabling this setting on Firefox is the only way I beat my Facebook addiction, but I'd rather use Chrome. Thanks!

This is a well-phrased request.  I think the distraction/mindfulness angle is important.

I'm not convinced the option you describe, even if we were willing to implement it, is the right solution.  I wonder if something like using a separate profile for "social media times" versus other times (much as I have separate work/home profiles), or an extension that limits access to certain websites, would make more sense.

As noted elsewhere, there are a number of fundamental design considerations in the omnibox built atop the premise of inline autocompletion; disabling this and providing a good user experience would require a complete rethink, and I don't think we want to go down that road.

I'm planning to leave this closed.

@pkasting, respectfully: you're wrong, it's undesirable, and that's why people keep asking for a fix.

Real life example:
If I type enter "furnace pump wires" and press enter, chromium returns a google search for "furnace pump wires".
If I then type "furnace pump" and press enter, chromium again returns a google search for "furnace pump wires".
That is not the desired outcome, and the described solution would provide the desired outcome.

Personally I only take issue with the fact that pressing enter submits the suggested string rather than the typed string, but I'd take any solution at this point.

I fully agree that inline autocompletion of multi-word search queries from local history is a net negative.  I personally think it should be removed.  Our metrics disagree with me.

That's distinct from "disable inline autocompletion entirely".  Reports of particular bad cases are generally welcome because we can sometimes tune the heuristics to behave better for everyone.

In any case, while I very well may be wrong (it happens a lot!), the omnibox team doesn't have any plans to do the fundamental redesign it would require to provide disabling inline autocomplete as an option, and Chrome's design ethos eschews options anyway.