zmuxuny opened a new issue, #7166: URL: https://github.com/apache/rocketmq-dashboard/issues/7166
### 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 @ 127c47b06a268cc74224d5f34c56ec7c36ac0d55. ### Runtime Environment Frontend component regression on Linux, Node 24, Vitest and Testing Library user-event. Chinese and English UI. No live-browser or deployed broker reproduction is claimed. ### Connected RocketMQ Cluster Not required: the defect is in the send-message form before any broker request. ### Build Toolchain _No response_ ### Describe the Bug The Topic send-message form renders each custom-property removal action as a bare MinusCircleOutlined with an onClick handler (web/src/pages/instance/topic.tsx near line1780). It has no semantic button, keyboard tab stop, or keyboard activation. Keyboard operators can add and fill properties but cannot use the offered removal action to repair a draft. ### Steps to Reproduce 1. Open a topic's Send message dialog. 2. Add several custom-property rows and enter their keys/values. 3. Focus a property's value and press Tab, then try to activate the row's minus/removal action with Enter or Space. 4. The removal icon is skipped by keyboard navigation. A mouse click can remove the row. The proposed regression uses real user-event typing/tab/keyboard, verifies the exact retained properties, and checks that removal neither submits the form nor sends a message. ### What Did You Expect to See? Each removal action is a focusable, named button. Enter/Space remove only the selected row, without submitting the message form. Remaining properties are preserved. ### What Did You See Instead? There is no keyboard-accessible removal control. On the unchanged production source, the final five-case regression file gives four failures (Chinese/English x Enter/Space cannot find a named removal button) and one passing pointer control;51 existing tests were unselected. The focused run took17.79s with no errors/resource-guard termination. ### Additional Context All-state issue/PR searches and actual diffs checked: #5586 covers five other mouse-only affordances; #5533/#3189/#3001 cover Topic/send localization; #6381 preserves property whitespace; #6615 covers backend property-wire validation. None changes this removal interaction. I plan a small semantic-button replacement retaining remove(name), with an explicit non-submit type and Chinese/English row-specific accessible names. AI assistance used for source investigation and the regression. No production fix has been applied yet. ### 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]
