Chrome misunderstands the Backspace button. Can it be fixed?

Question

Google Chrome

If you start typing something in the address bar, then Chrome turns on auto-completion and adds the most suitable option to the line. It's all great. Problems begin if I pressed the wrong letter. Naturally, after that I press Backspace, but Chrome does not delete the last letter typed, but what he himself thought up about the user input .
Correct behavior (as an option):
- auto-completed text should be gray, inactive until the user explicitly decides (Enter);
- the input caret should be located immediately after the letter that the user entered last;
- backspace should delete the letter that the user entered last;
- perhaps the delete button should delete the autocompleted text.
What can be done about it? Is there a setting for this behavior?
Should I write to the chrome bug tracker (do you agree that Chrome's behavior is incorrect)?

Answer 1

It seems to me that it is not necessary to designate it at least as a bug. It looks like a considered decision. Well, write somewhere to indicate that there are people who require a different behavior. Maybe there are already many of you.
Regarding what you wrote:
First of all, remember that the main feature of the omnibox is that you use it both to go to the site and to search for a word in a search engine. Hence the special behaviour. And the enter button, for example, is already packed here to go to Google or the site, and not to indicate the choice between the option you wrote and the option offered by chrome.
- auto-completed text should be gray, inactive until the user explicitly decides (Enter);
In your proposed solution, the user will have to explicitly press the down buttonfor example, after he started typing habr to indicate his choice, even if there is only one choice. In a standard use case, you will most likely choose the one that chrome offers. There will rarely be many options (unless you start with www ), and the browser will substitute the best one. So, from the point of view of user cases, forcing the user to make an extra click is unjustified.
It also happens that, for example, you enter habr to search it in Google, and the browser has already provided you with a link to the site, but you don’t want to go to the site. But this is also not a typical use case, for this it is worth pressing esc .
- the input caret should be located immediately after the letter that the user entered last;
It's just a question of whether you need to press esc once or 2 times in one situation. When you type habd instead of habr , you mistype the character. And it suggests habdahabr instead of habrahabr and you have to press esc twice . This situation is likely to be rare. Firstly, errors on average occur infrequently, since only a few characters are entered. Secondly , there is no habdahabr site in nature, which means it will not tell you anything.
I personally tried to reproduce this user case for a long time. He's definitely rare.
- backspace should delete the letter that the user entered last;
Well, the same thing. You are less likely to miss a letter and turn out to have a hint for your mistake than a chrome error with a hint. If you enter a keyword to search in Google, then it will most likely point you to the error after the search, giving other suggestions for the search. The user will not correct something in the omnibox here.
- perhaps the delete button should delete the autocompleted text.
The fewer buttons involved, the easier it is to teach the user.
In fact, such a campaign is probably justified and this is not a bug. It just seems unnatural to you because you haven't dealt with the omnibox and are trying to treat it like it's just an autocomplete text box.
In this case, Google is ready to put up with the dissatisfaction of users due to their habit, for their further convenience.