fix(desktop): CJK IME Enter blocked — draft never updates during composition

[questionjie-max]

Summary

Fixes #44135 — CJK IME users cannot send messages via Enter in the desktop composer.

Root Cause

Three remaining gaps after #39614 (which added flushEditorToDraft and removed the composingRef guard):

1. handleEditorInput left as no-op — after the composingRef guard was removed, the function body was empty. Draft state was never synced on input events, so the Send button stayed hidden during IME typing.

2. No auto-submit after IME Enter — imeEnterRef was already tracked in handleEditorKeyDown, but onCompositionEnd didn't check it. Enter is consumed by IME to commit the preedit, so submitDraft() never fires. Users needed a second Enter.

3. Blur doesn't reset stale composition flag — if compositionend is missed, the wedged composingRef permanently blocks the Send button ([Bug]: Desktop app composer Enter key has no effect — cannot send messages in new or existing sessions #44135 / fix(desktop): recover from a stale IME composition flag that silently blocks all sends #44149).

Fix (3 changes, 1 file: apps/desktop/src/app/chat/composer/index.tsx)

Change	Effect
handleEditorInput calls flushEditorToDraft()	Draft updates during IME → Send button appears
onCompositionEnd auto-submits on imeEnterRef	CJK one-Enter send
onBlur resets composingRef unconditionally	Stale flag can't permanently block sends

Testing

• macOS 15.6.1 with Simplified Chinese Pinyin
• Plain English: Enter sends normally (no regression)
• CJK Pinyin: "nihao" → Enter → commits AND sends in one step
• Send button: appears during IME typing, not only after punctuation

Related

• Diagnosed in [Bug]: Desktop app composer Enter key has no effect — cannot send messages in new or existing sessions #44135
• Complements fix(desktop): recover from a stale IME composition flag that silently blocks all sends #44149 (IME flag self-heal)
• Builds on [Bug]: Chinese Character Send Button Disappear Bug #39614 (flushEditorToDraft)

[liuhao1024]

⚠️ File encoding issue — is a base64 blob, not source code

The diff shows the entire 1,830-line replaced with a single base64-encoded line. The committed file appears to be binary-encoded rather than valid TypeScript/TSX source.

This will cause:

• Build failure (the bundler cannot parse base64 as TSX)
• The diff is unreviewable — the actual code changes are invisible

The file needs to be re-committed as plain text source. This typically happens when:

• A git filter or setting encodes the file as binary
• The file was edited in a tool that saved it in a non-UTF-8 encoding
• Force-pushing a corrupted working tree

Please re-commit the file with the intended source code changes, then the review can proceed.

[questionjie-max]

Fixed — the PR branch was rebuilt from upstream/main. The diff now shows only the actual changes (45 additions, 8 deletions, 1 file). Ready for re-review.

[teknium1]

Thanks for the focused CJK IME investigation. The stale composition-ref failure remains on current main, but this branch needs a targeted salvage rather than a direct merge.

Problems

• Current main already intentionally skips uncommitted preedit input at apps/desktop/src/app/chat/composer/index.tsx:303-312 and flushes committed text at :727-737 (commit 8e629b9f386d12b726bccb32e9d7b48402ea73ea), so the stated no-op input premise is no longer current.
• The new imeEnterRef is set at the PR's index.tsx:786-788 and cleared only at :1644-1645. A missed compositionend can therefore leave it armed and let a later unrelated composition end submit unexpectedly.
• No regression tests cover the new auto-submit or latch lifecycle; existing ime-composition-dom-repro.test.tsx:61-106 only covers committed-text visibility.

Suggested changes

• Resolve the stale-ref recovery into current main's composer structure and add focused tests for one-Enter submit, genuine-composition suppression, missed-composition-end recovery, and blur recovery.
• Reset the IME-enter latch on abort/new-composition paths as well as normal composition end.

Automated hermes-sweeper review.

[teknium1]

imeEnterRef is only cleared after a normal compositionend. In the missed-compositionend failure mode this PR also targets, it remains armed; a later unrelated composition end can then call submitDraft() without a new Enter. Reset this latch on abort/new-composition paths and add that regression case.

[teknium1]

This fix landed on main via #86760, which consolidated the duplicate PRs for this bug (earliest submission by @satotakumi in #37487; all contributors credited in that PR's body). Closing as the fix is now merged. Thanks for catching it!