I think what is happening here is that, once the search for an element in a dropdown is finished, the cursor is moved to end. This process happens very fast, so if you type too slow, it will search whatever you already typed and move you to the end.
I could reproduce this in a Discourse instance running version 2.8.0.beta9, in safe-mode. I’m not quite sure if this could be considered a bug, but it would be nice if the cursor stayed where you left it, instead of being moved to the end of the word. If you have a lot of long, complex tags, with similar format, I see how this could be annoying. What do you think? @joffreyjaffeux
Steps to reproduce:
- In any dropdown, for example the tags one in the composer, type any word.
- Put the cursor at the beginning of the word and type something else slowly. Or wait a couple second after finished typing.
- The cursor will be moved to the end of the word, even if you were still typing at the beginning.
As for the last thing mentioned, it was quite hard to reproduce. I don’t even think I got it right. But when I have the cursor over a tag in the dropdown, sometimes if a type a character slowly, it will be deleted and replaced by the next character I was writing. It’s too random, I don’t have the exact steps to reproduce:
You can see it at the end of the video: