Editing a workflow title is incorrectly updated during IME composition

[nzws]

Bug Description

When editing titles such as workflows, nodes, or credentials, pressing the Enter key while inputting text using an IME-based language such as Japanese incorrectly commits the edit.

See also: https://heistak.github.io/your-code-displays-japanese-wrong/otherthings.html#messaging-apps-do-not-directly-hook-to-the-enter-key-to-submit-messages-by-default

Screen.Recording.2026-01-17.at.0.03.56.mov

After investigating this issue, I found that there is a bug in EditableInput of Reka UI, the UI library on which n8n depends. I submitted a PR to fix this issue, and it has already been merged. Therefore, once Reka UI releases an updated version and n8n updates its dependency, this bug should be resolved.

unovue/reka-ui#2387

To Reproduce

1. Enable an IME
2. Click a workflow or similar title to enter edit mode
3. Start typing Japanese or another IME-based language and press the Enter key

Expected behavior

While IME composition is in progress, the input should not be committed. The edit should only be committed when the Enter key is pressed after IME input has been finalized.

Debug Info

Debug info

core

• n8nVersion: 2.2.4
• platform: npm
• nodeJsVersion: 22.21.1
• nodeEnv: production
• database: postgres
• executionMode: scaling (single-main)
• concurrency: -1
• license: enterprise (production)
• consumerId: e9e7ccd0-f90c-4412-aabb-56067a638828

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: database

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/143.0.0.0 safari/537.36
• isTouchDevice: false

security

• secureCookie: false

Generated at: 2026-01-16T14:50:37.620Z

Operating System

Alpine Linux v3.23

n8n Version

2.2.4

Node.js Version

22.21.1

Database

PostgreSQL

Execution mode

queue

Hosting

self hosted

[n8n-assistant]

Hey @nzws,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-6384".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-6384