openclaw - 💡(How to fix) Fix [Bug]: Control UI chat composer breaks accented characters (Spanish dead keys)

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

The chat input textarea in the Control UI webchat does not handle IME composition / dead key input correctly on Windows with a Spanish keyboard layout.

Steps to reproduce

1. Set Windows keyboard layout to Espanol (Espana) (0C0A:0000040A)
2. Open the Control UI webchat
3. In the chat input, try to type accented characters using dead keys (e.g., pressing ' then a to produce a)
4. Observe that the accented character is incorrect or garbled

Expected behavior

The chat composer should correctly handle dead key composition and produce the expected accented characters (a, e, i, o, u, n, etc.).

Actual behavior

Accented characters come out garbled. For example, typing a produces other incorrect characters like grave accents instead of acute accents.

OpenClaw version

2026.5.27

Operating system

Windows 11 (build 26200)

Install method

npm global

Model

xiaomi/mimo-v2.5

Provider / routing chain

openclaw -> xiaomi/mimo-v2.5 (local gateway)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

Affected: All users with Spanish keyboard layout using Control UI webchat Severity: Annoying (workaround available via copy/paste) Frequency: Every time dead keys are used Consequence: Accented characters are garbled, forcing users to type elsewhere and paste

Additional information

The same keyboard works perfectly in Word, Notepad, and other applications. The issue is specific to the Control UI chat input. Workaround: type in Word/Notepad and paste into the chat, or use Telegram channel instead (works correctly).