Users are reporting a critical bug affecting Japanese input methods (IME) on Discourse, where typing is interrupted before characters can be converted from Kana to Kanji. wenqin initially described the issue occurring in the chat box on macOS/Chrome, where incomplete kana fragments are sent directly instead of forming complete words. PuraGumi confirmed experiencing the same behavior when entering tag names in the New Topic UI across multiple operating systems and browsers, suspecting the issue stems from the input box triggering a tag search callback after every keystroke. While zogstrip noted they could reproduce the input selector correctly in their own tests, PuraGumi provided a video recording demonstrating the interruption. chapoi and maiki sought clarification on whether the bug affects chat specifically or tag inputs generally, with PuraGumi clarifying that while their example was tags, the underlying mechanism appears identical. The thread remains open with evidence submitted to help developers isolate the root cause.
The device the customer is using to chat and type is mac os/chrome.
Input method is Japanese input method.
His typing is interrupted when he is typing in chat, which prevents the chat from forming complete sentences.
It may be impossible to understand without using Japanese. Japanese input is to enter kana first, and when there are enough kana and it matches the pronunciation of a certain kanji word, the kana will turn into kanji for the typist to choose whether to enter it or not. However, because of this bug, the customer is currently interrupted in the middle of kana input. Instead, it is not possible to get to the kanji selection stage. When a kanji selection attempt is made, the typed kana is sent out directly. One by one, fragmented words are sent back, making it difficult to form complete sentences.
詳細：
本来の動作は、ローマ字の K → O を入力すると日本語の文字 KO に変換されるはずですが、代わりにインプットボックスがキーを押すたびにすぐに入力を中断し、K+O = KO ではなく、K、Oとなってしまいます。これは、インプットボックスがキーを押すたびにタグを検索するためにフォーラムサービスにコールバックしようとしているためだと推測されます。
