Open PhantasWeng opened 1 year ago
Any suggestions?
@PhantasWeng sorry for the delayed response, I'm trying to clean up our issues now. Is this still an open topic? I would expect this to be a general issue with the Autocomplete UI and not limited to Docusaurus. May I ask you test the behavior on other DocSearch (Autocomplete UI) sites? See here for some featured partners: https://docsearch.algolia.com/. For example, neither Bootstrap nor Material use Docusaurus.
@randombeeper Yes, this issue still exists.
I encounter the same problem in different environments, which is why I am raising this issue here instead of on Docusaurus.
Hi @randombeeper,
Here is a reference regarding events related to non-Latin IME: Composition Event
For non-Latin IME, such as Chinese and Japanese, we typically use compositionstart and compositionend to determine input.
You can trigger the input change event using compositionend instead.
Could you let me know which file contains the program that triggers the event? I believe I could also contribute.
I also encountered the same problem in Vue.js doc. But it works fine in Docsearch doc. I guess this problem has been fixed in a recent release?
Description
In Chinese and Japanese input methods, character selection is done using pinyin and enter key.
For example: to input "你" (ㄋ一ˇ), you would type
ㄋ + ㄧ + ˇ + enter
to select the character. Currently, pressing enter triggers an incorrect input.This results in submitting
ㄋ一ˇ
instead of你
.Steps to reproduce
DocSearchModal > input
ㄋ一ˇ enter
(key mapping to su3 enter)Expected behavior
Expected to be a character selection on first enter keypress.
For example, in chrome url input
In github text area
Environment