Media selection modal: "Choose from existing" rows are not clickabl

[nabilAhmedN]

Describe the Bug

Description
using an upload field in the Payload admin panel and clicking "Choose from existing", the media list opens but the rows/images are not clickable. There is no way to select an existing media file.

Steps to Reproduce

1. Open the Payload admin panel2. Go to a collection with an upload field (e.g., Pages → Home → Hero Image Carousel).
2. Click "Choose from existing".
3. Try clicking on any media row/image in the modal.

Expected Behavior
Clicking a media row should select it and close the modal, attaching the file to the field.

Actual Behavior
Clicking on a row does nothing. modal stays open and no file is selected.

Workaround
Uploading a new file with "Create New" or drag-and-drop works. Only selecting existing files is broken.

Environment

• Payload version: 3.85.1
• OS: Windows
• Browser: (Chrome/Edge/etc.)

Screenshots

Link to the code that reproduces this issue

I can provide a minimal reproduction repository if needed. This occurs in any Payload v3 admin panel with an upload field using the "Choose from existing" media picker.

Reproduction Steps

1. Start a Payload v3 project with an upload field (e.g., an image field in a global or collection).
2. Go to the admin panel and open the field.
3. Click "Choose from existing".
4. In the media modal, try clicking on any existing media row/image.
5. The modal does not close and the file is not selected.

Which area(s) are affected?

area: ui

Environment Info

Payload: 3.85.1
Next.js: 16.2.9
Node.js: 22.19.0
OS: Windows
Browser: Chrome/Edge
Package manager: npm

[github-actions]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@latest -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload