-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emoji autocomplete delay is too high by default #19333
Comments
I don't think I can reproduce though I am not 100% sure I understand what you're describing, could you perhaps record a video of this? |
@SimonBrandner Sure! 😊 This is the result after typing Kooha-10-09-2021-14-32-10.mp4As you can see, it is the same result as if I just typed That is because the autocomplete pop-over took longer to appear than the time it took me to hit TAB, so the emoji was not autocompleted nor inserted in the input text bar. |
@SimonBrandner Yeah, that works thanks! 😊 It was set to 200 ms. With 100 ms I can still hit this issue occasionally. I set it to 50 ms and now I am unable to reproduce the issue. 🎉 I would say this issue could be rephrased to: lower the default autocomplete delay from 200 ms to 50 ms. Is there any reason to have a higher value by default? |
Great!
I am not sure, let's make this a feature request then |
Also, until a few months ago the first autocomplete (whether a username or emoji autocomplete) was instantaneously inserted, so you could go on with your life if you wanted the first result, and only needed to use the popup if you really wanted to choose another emoji/username. Now, you always need at least two keypress to insert an emoji/username. 😩 |
@yanndinendal I don't think that is related to this issue. 🤔 |
Yes, sorry. It may be related if someone (like me) searches if there are issues regarding the fact that it has now become slow to autocomplete. But yes, sorry for the Off Topic, this one is about the time it takes to open it, not the time it takes to validate it. |
Steps to reproduce
Type
:blus<TAB>
fast, where<TAB>
is simply the TAB key.Outcome
What did you expect?
I expected
:blus<TAB>
to insert the 😊 emoji in the chat input bar.What happened instead?
I can see
:blus
written in the input bar, with a pop-over with one emoji autocomplete suggestion only (:blush:
), but the<TAB>
key was forgotten/ignored.Overall, it felt too slow to respond, when compared to other services like Telegram or Google Meet, where the autocomplete feels instantaneous and
:blus<TAB>
would always insert 😊 no matter how fast you type.Operating system
No response
Application version
1.9.0
How did you install the app?
dl.flathub.org
Homeserver
No response
Will you send logs?
No
The text was updated successfully, but these errors were encountered: