Auto-complete functioning as auto-correct ("fav:username" -> "favfavver2")

Just a minor grievance.

Now that the search field interprets Enter as auto-complete by default, when typing "fav:username" as the last tag in a search, one has to wait about two seconds after the completion of the username before pressing enter; otherwise it will be auto-corrected to "favfavver2."

It seems at first glance to be something we just have to live with, but it might also have a nice solution.

normally suggestions like favfavver2 would disappear when a character is typed that does not match the next character in their name, but a ":" does not accomplish the same thing.

I can't think of any case where that is useful behavior.

Something worthy of note is that typing "id:#####" does not come with the same complications. Once the semicolon is typed, all suggestions disappear.

Thank you for your time and continued work on Danbooru.

I was recently having a similar problem with enter - if I type something (not necessarily fav:whatever, just any tag) and then hit enter to search it will instead autocomplete the first result, whether that result is right or not.

A simple way to fix both of these problems would be to remove enter-to-complete so that it doesn't conflict with enter-to-submit. Then the tab key could be used as the sole keyboard shortcut for autocomplete - I don't think we need more than one anyway.

i've experienced something similar in the tag edit box. if i typed initially, 5girls by mistake, then tried to correct it by moving the cursor back and replacing 5 with 2, autocomplete is invoked completing 2girls anew and moving the old 'girls' (from 5girls) one space ahead. this creates two tags 5girls and girls.

i cleaned the girls tag recently and i assumed the recent population was created due to similar circumstance when users didn't realized a word fragment was left behind.

since i find autocomplete useful and didn't want to turn it off, i get around with this by pressing 'esc' key to close autocomplete.

Toks said:

A simple way to fix both of these problems would be to remove enter-to-complete so that it doesn't conflict with enter-to-submit. Then the tab key could be used as the sole keyboard shortcut for autocomplete - I don't think we need more than one anyway.

I'm in favor of this as well, especially considering that on the post sidebar there are no other form elements to tab to in the first place.

Thirded. Pressing enter while the input focus is on an input box should submit the form regardless of circumstances. It's never a good idea to modify basic UI behaviour like that. It's been several times that it messed up my search.

If Danbooru's built-in autocomplete switches to tab-to-complete, I'll finally have a reason to ditch DanbooruUp.

I removed enter-to-complete for the next version.

Thanks for changing it!