beautyarbutin opened a new issue, #4465: URL: https://github.com/apache/rocketmq-dashboard/issues/4465
### Before Creating the Bug Report - [x] I have searched the existing issues and pull requests. - [x] I am using the latest `master` branch (`987b748e8f4f421c5cd3c4c4e51a064cc7e59f18`). ### Bug description The Topic and Consumer resource tables keep selected row keys when the visible result scope changes. A user can select a row, then search, filter, or move to another page. The row disappears, but the batch-delete action still includes it. On the Topic page, the selection also survives an instance switch. Confirming the action can therefore send topic names selected under the previous instance together with the newly selected instance ID. ### Steps to reproduce 1. Open the Topic or Consumer page and select one row. 2. Apply a search/filter, change the table page, or (for Topic) switch the selected instance so that the selected row is no longer visible. 3. Observe that the batch-delete count is still present. 4. Confirm batch deletion. ### Actual behavior The delete request includes resource names that are no longer visible in the current result scope. For Topic instance switches, the stale names are submitted with the current instance ID. ### Expected behavior Batch selection should be scoped to the current visible query/page/instance. When that scope changes, hidden selections should be cleared so the delete request can only contain rows the user can currently inspect. ### Proposed scope - Reset Topic selections when instance, search, type filter, page, or page size changes. - Reset Consumer selections when search, mode filter, page, or page size changes. - Add frontend regression tests for both resource pages. Issue #1720 discussed broader Topic-page state reset behavior on instance changes. This report is narrower: it concerns hidden batch selections and also affects Consumer query/page changes. ### Environment - Browser: current Chrome - RocketMQ Dashboard branch: `master` -- 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]
