Chrome Version: (copy from chrome://version)OS: (e.g. Win10, MacOS 10.12, etc...)What steps will reproduce the problem?(1) Search for something like "skyrim frostfall vs"
(2) Search for a new query which the 1st query starts with, such as "skyrim frostfall"
(3) Observe that it was auto-completed to the 1st query so when we press enter quickly thereafter, we are wrongly taken to the 1st query which. I know what I typed so I'm not always looking at the screen to verify it. Often I will not even see that it was autocompleted until AFTER the reuslts show up. I will wonder "wow, why are the results so irrelevant?" Then I will realize, "oh yes, it's the stupid auto-complete again", and have to type it in again. This makes for a terrible user experience.
What is the expected result? Ability to disable this auto-complete "feature" which is useless for people who type above 140 wpm.
What happens instead? The auto-complete "feature" is forced upon us and results in very unexpected behavior which is disorienting and confusing.
Chrome Version: (copy from chrome://version)OS: (e.g. Win10, MacOS 10.12, etc...)What steps will reproduce the problem?(1) Search for something like "skyrim frostfall vs"
(2) Search for a new query which the 1st query starts with, such as "skyrim frostfall"
(3) Observe that it was auto-completed to the 1st query so when we press enter quickly thereafter, we are wrongly taken to the 1st query. I know what I typed so I'm not always looking at the screen to verify it. Often I will not even see that it was autocompleted until AFTER the reuslts show up. I will wonder "wow, why are the results so irrelevant?" Then I will realize, "oh yes, it's the stupid auto-complete again", and have to type it in again. This makes for a terrible user experience.
What is the expected result? Ability to disable this auto-complete "feature" which is useless for people who type above 140 wpm.
What happens instead? The auto-complete "feature" is forced upon us and results in very unexpected behavior which is disorienting and confusing.
Chrome Version: (copy from chrome://version)OS: (e.g. Win10, MacOS 10.12, etc...)What steps will reproduce the problem?(1) Search for something like "skyrim frostfall vs"
(2) Search for a new query which the 1st query starts with, such as "skyrim frostfall"
(3) Observe that it was auto-completed to the 1st query so when we press enter quickly thereafter, we are wrongly taken to the 1st query. I know what I typed so I'm not always looking at the screen to verify it. Often I will not even see that it was autocompleted until AFTER the reuslts show up. I will wonder "wow, why are the results so irrelevant?" Then I will realize, "oh yes, it's the stupid auto-complete again", and have to type it in again. This makes for a terrible user experience.
What is the expected result? Ability to disable this auto-complete "feature" which is useless for people who type above 140 wpm. The amount it takes for us to see and recognize that our words are being auto-completed, is LONGER than the amount it takes to type it all out in the first place!
What happens instead? The auto-complete "feature" is forced upon us and results in very unexpected behavior which is disorienting and confusing.
I agree, that suggestion looks annoying, and shouldn't be suggested at that moment. We know that Chrome suggests previously-issued search queries too aggressively, and we're working on turning this back.
If you want to help, we could use examples like this of where it misbehaves.
Send us the chrome://omnibox output of times where the omnibox doesn’t do what you want, such as for "skyrim frostfall". Ideally we should be able to make the omnibox smart enough that an option to disable inline autocomplete isn't necessary. (I'm sorry to report that such an option has been vetoed; see bug 91378 .)
When reporting chrome://omnibox output, check both the "show all details" and "show results per provider" boxes. This will help us figure out what's going wrong in this particular case.
Feel free to paste the results in here unformatted; we’ll be able to decipher them.
thanks, and sorry.
Comment 1 by mloh@google.com
, Oct 12