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
Attach wanakana to a textarea using wanakana.bind (the wanakana website works fine for testing this)
Focus the textarea
Activate a Japanese IME
Type a word in the search bar that can be converted to something that contains half width latin characters (for example えいご which can convert to A5)
Attempt to convert the word to kanji using space and press space multiple times
Keep pressing space until you hit the latin character conversion
Upon hitting the latin character conversion in your IME, wanakana jumps in and kills the IME. In this example with えいご it is impossible for someone to convert えいご to an IME entry below the conversion of A5. Wanakana will convert A5 to ア5 regardless of if the user is still composing from the IME. (https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/isComposing)
Reported by a user using Google IME on Windows. Replicated by me using Mozc on Linux with both Firefox and Chromium.
The text was updated successfully, but these errors were encountered:
Kuuuube
changed the title
Wanakana bind prevents external IME from converting when using space for conversion
Wanakana bind prevents external IME from converting when hitting a conversion containing latin characters
Mar 10, 2025
To reproduce:
wanakana.bind
(the wanakana website works fine for testing this)えいご
which can convert toA5
)Upon hitting the latin character conversion in your IME, wanakana jumps in and kills the IME. In this example with
えいご
it is impossible for someone to convertえいご
to an IME entry below the conversion ofA5
. Wanakana will convertA5
toア5
regardless of if the user is still composing from the IME. (https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/isComposing)Reported by a user using Google IME on Windows. Replicated by me using Mozc on Linux with both Firefox and Chromium.
The text was updated successfully, but these errors were encountered: