zmuxuny opened a new issue, #7087: URL: https://github.com/apache/rocketmq-dashboard/issues/7087
### 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 Linux, Node 22+, Vitest/jsdom; real K8s certificate page with a deferred service response. ### Connected RocketMQ Cluster Not required: frontend dialog lifecycle reproduction with mocked certificate services. ### Build Toolchain _No response_ ### Describe the Bug The creation modal can be cancelled while its request is pending. If the operator reopens it and enters another certificate, the first request success callback unconditionally closes the modal and resets the shared form, losing the new unsent draft. ### Steps to Reproduce 1. Open Add certificate, fill identity and cluster, and submit while delaying createK8sCert. 2. Cancel and reopen Add certificate. 3. Enter a different identity and cluster. 4. Complete the first request successfully. ### What Did You Expect to See? The completed creation should appear in the inventory, but only its originating dialog session may be closed/reset or have its loading state updated. A newer draft must survive. ### What Did You See Instead? The newer draft is cleared and the modal closes. The real component regression on unchanged production code fails: expected second-cert, received an empty string. ### Additional Context Searched all-state certificate modal/cancel/reopen/draft/delayed-completion issues and PRs. Existing duplicate-submit #1617 and concurrent-delete #5404 concern different boundaries. Scope is dialog ownership across reopening, not certificate parsing or the server mutation. AI assistance was used for source analysis and test drafting. ### 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]
