Fix[Alt Generation]: Generate button becomes unresponsive after using Next/Previous in media modal

[yogeshbhutkar]

What?

Closes #627

Fixes the Alt Text Generation button becoming unresponsive after using Previous/Next inside the media modal.

Why?

The media modal replaces or refreshes the attachment details UI during navigation. The existing initialization only handled the initial modal state, so the Generate/Regenerate button could lose its event binding after moving to another attachment.

How?

Bind to the media edit frame’s refresh event after the edit attachment modal is first opened. This re-initializes the alt text controls when the modal refreshes for Previous/Next navigation, while ensuring the refresh handler is registered only once to avoid duplicate generation requests.

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

1. Go to Media → Library.
2. Select an image and generate alt text.
3. Use the modal’s Previous/Next controls to navigate to another image.
4. Confirm the Generate/Regenerate button still works.
5. Close and reopen the media modal, then generate alt text again.
6. In the Network tab, confirm each Generate/Regenerate click sends exactly one request.

Screencasts

Before

before.mov

After

after.mov

Changelog Entry

Fixed - Alt Text Generation button becomes unresponsive after using Next/Previous in the media modal.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.45%. Comparing base (77f116e) to head (f93f0e5).

Additional details and impacted files

@@            Coverage Diff             @@
##             develop     #631   +/-   ##
==========================================
  Coverage      74.45%   74.45%           
  Complexity      1740     1740           
==========================================
  Files             85       85           
  Lines           7521     7521           
==========================================
  Hits            5600     5600           
  Misses          1921     1921           

Flag	Coverage Δ
unit	74.45% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

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.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @kohcsi.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: kohcsi.

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.

[jeffpaul]

Works as expected via Playground testing, thanks!

[jeffpaul]

@kohcsi if you're able to confirm your WordPress.org username (and ideally link it with your GitHub account), then I can ensure its properly credited in the AI plugin release (and associated AI Contributor badge)... thanks!