xtermjs/xterm.js

In macOS Chrome + AquaSKK (Input Method), Some characters will not converted by IM

Open

#5,348 opened on 2025年6月4日

GitHub で見る
 (0 comments) (5 reactions) (0 assignees)TypeScript (16,196 stars) (1,574 forks)batch import
area/imehelp wantedtype/bug

説明

https://github.com/microsoft/vscode/issues/184777

Details

  • Browser and browser version: Google Chrome 137.0.7151.69 (Official Build) (arm64)
  • OS version: macOS 15.5（24F74）
  • xterm.js version: I'm not really sure, but tested on VSCode 1.100.2 and https://xtermjs.org/ example

Steps to reproduce

  1. Enable Hiragana Input in AquaSKK https://github.com/codefirst/aquaskk/releases (by enable AquaSKK input and press Ctrl-J)
  2. Type an character which only needs one type (e.g. "a" for "あ", "i" for "い", "-" for "ー")
  3. If xterm.js is running on Chromium-based runtime, these characters would not converted by IM and just put actual typed keys (press: "a", expected to see: "あ", actual: "a")

Note:

  • If browser isn't Chromium-based (e.g. Safari and Firefox), it would work fine.
  • If character requires two or more types (e.g. "ka" for "か"), we could see after converted character in xterm.js even in Chromium-based browser

I think It is because of differences about how browser fires input events, so I will attach screenshot of https://w3c.github.io/uievents/tools/key-event-viewer.html (I typed "aka", expected result is "あか"):

Image

Top one is the Chrome, Left one is the Safari 18.5 (20621.2.5.11.8), Right one is the Firefox Nightly 141.0a1 (2025-06-03) (aarch64)

コントリビューターガイド

技術スタック
typescriptjavascript
領域
frontendinternationalization
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
half day
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
fresh
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Understanding of IME (Input Method Editor) eventsFamiliarity with browser key/composition events
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
40
調査方針
Investigate the difference in how Chrome/Safari/Firefox fire input events during IME composition, focusing on the `beforeinput` and `input` events. Review the linked VSCode issue (#184777) for potential fixes. Examine xterm.js's input handling code (likely `src/InputHandler.ts`) to see how it processes composition events. Consider adding handling for the `compositionstart`, `compositionupdate`, and `compositionend` events to properly support IMEs on Chromium based browsers.
In macOS Chrome + AquaSKK (Input Method), Some characters will not converted by IM · xtermjs/xterm.js#5348 | Good First Issue