Skip to content
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

Input method problem #26

Open
NoverNobida opened this issue May 12, 2021 · 2 comments
Open

Input method problem #26

NoverNobida opened this issue May 12, 2021 · 2 comments

Comments

@NoverNobida
Copy link

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.

@xvvvyz
Copy link
Owner

xvvvyz commented May 12, 2021

@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.

@BaccanoMob
Copy link

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)
image

With my fork with autoFocus disabled,
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants