[jubianchi]

Problem

While an input method editor composes a word (Japanese, Chinese, Korean), the arrows move through its candidates and Enter confirms the word. The browser still delivers those keydowns to the page, flagged isComposing, and the search dialog's onKeyDown acted on them, unlike the issue command, the mention textarea and the conversation thread, which already check event.nativeEvent.isComposing.

Type nihongo with a Japanese IME and press Enter to confirm 日本語: the provisional query matches nothing, so the options are the suggested searches, and that Enter replaces the word with "shipping a side project". When picking a recipient for a remote, it picks whichever developer the half-typed name matched. The arrows move the active result instead of the IME's candidates.

Checked locally with keydowns dispatched with isComposing: true on the empty dialog:

Composing key	Before	After
Enter	field set to "shipping a side project", default prevented	nothing
ArrowDown	selection moves to the second suggestion	nothing

The same keys without composition keep working after the change.

Changes

1. onKeyDown returns early while composing, so the IME keeps the keys.
2. tests/Unit/SearchDialogComposition.test.tsx, red before and green after: composing Enter and ArrowDown leave the value and the active option alone and never prevent the default; the plain keys still move the selection and pick a suggestion.
3. The test is listed in tests/draft-images.config.ts and tests/tsconfig.json; trivial conflicts with test: run the ten component tests that CI never ran #492 and fix: refresh the shared clock when the first component subscribes again #517, which touch the same lists.

[brendt]

Thanks!