Skip to content

Windows Japanese IME preedit text is not visible and candidate window is offset #10146

@snuffxxx

Description

@snuffxxx

Discord username (optional)

No response

Describe the bug

On Windows, Japanese IME input does not render the preedit / composing text correctly in Warp, and the IME candidate window appears offset above the actual input area instead of near the caret/composition position.

This still reproduces on the latest Warp version after trying the common input/font workarounds.

To Reproduce

  1. Open Warp on Windows.
  2. Use Japanese IME in the normal Warp input area.
  3. Type Japanese text and start IME conversion.
  4. Observe the composing text and candidate window position.

Expected behaviour

  • The Japanese IME composing/preedit text should be visible while converting.
  • The IME candidate window should appear at the current caret/composition position.

Screenshots

I have a screenshot showing the candidate window appearing above the input area. I can attach it manually if needed.

Operating System

Windows

OS Version

10.0.26200

Shell Version

No response

Warp Version

v0.2026.04.29.08.57.stable_01

Additional context

I tried the following, but the issue still reproduces:

  • Updated Warp to the latest version
  • Switched to Classic Input / Shell (PS1)
  • Changed Input position
  • Set a Japanese-capable font

This does not appear to be a shell, font, or input mode configuration issue. It looks related to Windows IME marked text rendering and IME candidate window positioning.

Related issue: #320

Does this block you from using Warp daily?

Yes

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:terminal-inputTerminal command-line input, cursor movement, key handling, and input editing.bugSomething isn't working.duplicateThis issue or pull request already exists.os:windowsWindows-specific behavior, regressions, or requests.repro:highThe report includes enough evidence that the issue appears highly reproducible.triage-reviewedtriagedIssue has received an initial automated triage pass.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions