You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
East Asian scripts are not letters, such as 中国한국にほん. In East Asia, we use the keyboard to type characters through "multiple letter combinations".
However, when typing in Tilde, it will appear that the first character is always an English letter instead of an East Asian character.
The text was updated successfully, but these errors were encountered:
@NoverNobida thanks for opening this. After logging a few keypresses, the first character is indeed a normal English letter keypress and the event doesn't indicate any "composing" of a script. Because of this, I'm not sure how we can differentiate the events to fix this bug. It may be a hard limitation of dynamically showing the search form.
Hey @NoverNobida check my fork of this. With autoFocus disabled in the config, IME should work as if typing in a typical input field.
I believe the cause is triggered when search box is focused, the IME gets interrupted. Possible solutions would be to introduce a dummy prefix (like !, 1) so the parser ignores the first keydown if its the dummy prefix. Or have the search box open at times to avoid this (like my fork)
With autoFocus enabled/or this repo, (I clicked outside for every single character to show focus is the cause)
East Asian scripts are not letters, such as
中国
한국
にほん
. In East Asia, we use the keyboard to type characters through "multiple letter combinations".However, when typing in Tilde, it will appear that the first character is always an English letter instead of an East Asian character.
The text was updated successfully, but these errors were encountered: