iloveeyjafjalla opened a new issue, #6618: URL: https://github.com/apache/rocketmq-dashboard/issues/6618
### Before Creating the Bug Report - [x] Searched current open/closed Issues and PRs, read related public comments and actual patches, and completed the current open-PR file index for these files. - [x] This concerns RocketMQ Studio's navigation search, with source and test limits below. ### Studio Version `rocketmq-studio`, `779b8c0e7aed2396d3cc72743dcd544ea48e9ae6`, tested from source with the existing Vitest/jsdom toolchain. ### Runtime Environment / Connected RocketMQ Cluster Windows local frontend test process, Node 24.15.0, npm 11.12.1. Real MainLayout, Ant Design Modal/Layout, providers and MemoryRouter; standard DOM composition/keyboard events are supplied at the input boundary. No native input-method/device/browser session, cluster, database or deployment was used or claimed. ### Describe the Bug MainLayout's navigation-search input branches on Enter/ArrowUp/ArrowDown without checking whether the event belongs to text composition. Enter therefore opens a matching page and closes/clears the palette while confirming composed text. A composing arrow can also change the page selected by the next ordinary Enter. ### Steps to Reproduce The deterministic component reproduction included in the linked PR follows the real navigation controls: 1. Render MainLayout on the home route and click “打开导航搜索”. Wait for the real input to be visible. 2. Start a composition session and update its query to `设置`, which has a real matching navigation entry. 3. Dispatch the confirming Enter with `isComposing: true`. A separate case covers Enter with `keyCode: 229` after composition end, consistent with the existing Composer fallback. 4. Old code renders the Settings route outlet immediately and closes the search instead of retaining the query. A composing ArrowDown likewise alters the selected navigation result; an ordinary ArrowDown/Enter control still works. Expected: keep composition keys available to the input method; keep the palette/query and route until a subsequent ordinary navigation key. Actual: composition confirmation or selection is also interpreted as palette navigation. ### Additional Context [UI Events §3.6.5](https://w3c.github.io/uievents/#events-composition-key-events) describes keyboard events during composition. This report demonstrates the component's response to those events, without claiming an observed native IME incident. #6376/#6358 and #6070/#6067 cover different input components, and their actual patches do not protect MainLayout. Final old production run: 3 meaningful route-assertion failures, 1 normal-navigation control pass. Repaired related suites: 16/16; lint 0 errors/10 unchanged warnings, build/license 133/140 and formatting passed. The test provider disables motion; earlier setup visibility failures are retained as experiments, not product evidence. No timeout or old assertion was weakened. Independent review completed; AI assistance (Codex) disclosed. No full frontend/backend or remote CI pass is claimed. ### Are You Willing to Submit a Pull Request? - [x] Yes: https://github.com/apache/rocketmq-dashboard/pull/6617 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
