[Request Logs]: Fix focus loss on interaction with Purge Actions - #599
Conversation
Sorry, something went wrong.
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## develop #599 +/- ##
==========================================
Coverage 73.18% 73.18%
Complexity 1731 1731
==========================================
Files 85 85
Lines 7473 7473
==========================================
Hits 5469 5469
Misses 2004 2004
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry.
|
Sorry, something went wrong.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. Co-authored-by: yogeshbhutkar <yogeshbhutkar@git.wordpress.org> To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Sorry, something went wrong.
What, and Why?
Adds focus management for the request logs purge confirmation flow. When Purge All Logs is clicked, focus moves to Cancel in the confirmation UI. When either Cancel or Yes, Purge All closes the confirmation UI, focus returns to Purge All Logs.
See #589
How?
Uses simple callback refs to focus conditionally rendered buttons as they mount.
Use of AI Tools
AI assistance: Yes
Tool(s): Codex
Model(s): GPT-5.5
Used for: Initial code skeleton; final implementation was reviewed and edited by me.
Testing Instructions
Screencast
Before
before.movAfter
after.movChangelog Entry