zmuxuny opened a new issue, #7098: URL: https://github.com/apache/rocketmq-dashboard/issues/7098
### 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 Frontend component regression tests on Linux, Node 24.19.0, Vitest/jsdom, real Ant Design Select and Slider components, Chinese and English locales. ### Connected RocketMQ Cluster Not broker-specific. Mocked queue data for broker-a and broker-b, queue 0, exposes the control naming issue without a live cluster. ### Build Toolchain _No response_ ### Describe the Bug QueueBrowser exposes its topic picker and per-queue offset sliders without accessible names. The message-detail close buttons expose only the generic close icon name, with no queue identity. With multiple queues/detail cards, assistive-technology users cannot identify which control affects which queue. The topic placeholder is visible but does not name its combobox. ### Steps to Reproduce 1. Render QueueBrowser in either Chinese or English. 2. Inspect the topic combobox accessible name. 3. Load a topic with queues on two brokers and inspect the offset slider accessible names. 4. Open a queue message detail and inspect its close button name. 5. Use keyboard ArrowLeft to change a selected offset and Enter to close a detail card. ### What Did You Expect to See? The topic picker has a localized topic name. Each offset slider identifies its broker/queue, and each close button identifies its message-detail card. Existing keyboard slider and close behavior should remain functional in both locales. ### What Did You See Instead? The topic combobox and both offset sliders have empty accessible names, and the detail close control cannot be located by a queue-specific accessible name. Two locale regressions fail six name assertions before production changes. ### Additional Context Searched QueueBrowser/accessibility, queue/slider and queue/accessible issues and PRs; related localization changes #5559 and #5220 do not name these controls. Regression tests exercise the real controls and will also check keyboard offset and close interactions. ### 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]
