zmuxuny opened a new issue, #7133: URL: https://github.com/apache/rocketmq-dashboard/issues/7133
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository and believe that this is not a duplicate. - [x] This is a defect in RocketMQ Studio, not a usage question and not a defect in another Apache RocketMQ repository. - [x] I can reproduce this on the current `master` branch, or I have stated the exact version I am running below. ### Studio Version rocketmq-studio at 127c47b06a268cc74224d5f34c56ec7c36ac0d55 ### Runtime Environment Web frontend, reproduced with real MainLayout, Ant Design Menu and React Router under the repository Vitest/jsdom setup. No live cluster is needed. ### Connected RocketMQ Cluster Not applicable: this is application-shell navigation for the existing AI conversation route. ### Build Toolchain _No response_ ### Describe the Bug The AI navigation item is selected on /ai but loses its selection when a conversation opens at /ai/c/<conversationId>. MainLayout uses the complete pathname as the menu key even though the AI menu entry has key /ai. The nearby isAiRoute test also only recognizes exact /ai, so the same supported conversation route receives a different declared content overflow policy. ### Steps to Reproduce Open /ai, then open or create a persisted conversation so the route becomes /ai/c/7 (any existing conversation ID). Observe the AI sidebar item. Also open /ai/ or /ai/c/7/ directly. Deterministic regression: render real MainLayout and Ant Design Menu with MemoryRouter and inspect ant-menu-item-selected before and after navigation. ### What Did You Expect to See? All supported AI routes should select the AI menu item and use the same AI content policy. Leaving AI should select the new section. Unrelated paths such as /aix, /ai-tools and /ai/c/7/extra must not be classified as AI. ### What Did You See Instead? On unchanged production, four cases fail: /ai/, /ai/c/7, /ai/c/7/, and navigating from /ai to a conversation. The AI menu item has no selected class. The /ai case and five unrelated-path controls pass. This confirms navigation/state mismatch; no browser scrolling defect is claimed from jsdom. ### Additional Context All-state issue/PR searches covered AI sidebar/navigation/highlight, selectedMenuKey, isAiRoute, MainLayout and /ai/c. Nearby MainLayout patches #5025, #5338 and #4606 were checked and do not normalize AI conversation selection. The bounded fix can reuse React Router matchPath for the same two routes declared in App.tsx; no new route, dependency or UI text is needed. AI assistance used for investigation and regression tests. ### Are You Willing to Submit a Pull Request? - [x] Yes, I am willing to submit a pull request. -- 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]
