Allow us to completely disable omnibox search, current behaviour is awkward
Reported by
djbrain...@gmail.com,
Oct 10
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: Type something in the omnibox and the first suggestion is the google search for it. Even if the entered value is an url to browse to. Especially with localhost or custom local domain names without a point in it. Even more a problem when you just want remove a hashtag from the url, it's almost impossible to get to that required page. What is the expected behavior? No search suggestion, always goto entered url/value instead. Completely disable omnibox search suggestion. I do not require the search, in any case. What went wrong? See attached file which provide you the awkward behaviour. It's unpredictable and greatly slow down my workflow. It's almost impossible to get to my required url, even if i manually enter http:// Did this work before? N/A Chrome version: 69.0.3497.100 Channel: stable OS Version: 10.0 Flash Version: I personally don't like the google search become the first suggestion when i type something in the address bar. I do my work on localhost host and most of the time when i enter some url without http:// and when i hit enter it redirects me to the google search instead of just browsing to the url. This doesn't happen everytime and is unpredictable. I never need to the google search in the address bar so an option to completely disable this would be aweseome.
,
Oct 17
djbrainnrg@ Thanks for the issue. As per the above description, this looks like a feature request to allow to disable omnibox search which shows google suggestions first. Marking this as Untriaged for further updates from Dev. Thanks..
,
Oct 18
The main awkward behavior is with #hash fragments. That was definitely a bug. It was only fixed for Chrome 71, so it's likely you'll be living with it for a while. One way to fix it would be to delete the visits in your history that autocomplete with the hashtag. It's the #hash that is causing the trouble. If you have other examples of awkwardness, please send them along. (File new bugs.) We'd love to improve the omnibox suggestion system. We need examples where the omnibox doesn’t do what you want (ideally with chrome://omnibox details). Ideally we should be able make to make the omnibox smart enough that such an option to disable parts of it isn’t necessary. |
|||
►
Sign in to add a comment |
|||
Comment 1 by susan.boorgula@chromium.org
, Oct 11