Skip to content

fix(web): preserve IME input in voice-tag controls - #550

Merged
remsky merged 1 commit into
remsky:masterfrom
abaichuan1017:fix/voice-tag-ime-enter
Oct 28, 2026
Merged

remsky merged 1 commit into
remsky:masterfrom
abaichuan1017:fix/voice-tag-ime-enter

Conversation

@abaichuan1017

Copy link
Copy Markdown
Contributor

Enter used to confirm an IME composition also creates a voice tag or commits its rename; Enter/Escape in voice search closes the dropdown mid-composition. Ignore composing key events in those three handlers and preserve their normal keyboard actions afterward.

Added three regression cases covering creation, rename, and search; all fail on the original handlers. Validation: npm run test:web (113 passed), npm run test:e2e -- --reporter=line (41 passed), and git diff --check. A Chromium check with synthetic composing key events also confirmed that composing Enter leaves the cast unchanged and the following ordinary Enter creates the tag. Backend calls were mocked; no TTS inference was performed.

@remsky

remsky commented Oct 28, 2026

Copy link
Copy Markdown
Owner

Thanks for the PR and test cases! Also opened #556 for the same issue noticed in the TextEditor find/replace inputs

@remsky
remsky merged commit 01b3dff into remsky:master Oct 28, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants