Image upload after dirty filter requires filter change before it can be inserted to page

[utkarshpatel]

Steps:

1. Open media library popup.
2. Change date filter.
3. Upload new image.
4. See uploaded image is not visible in list nor selectable. (Select button is disabled)
5. Change filter to match the new image uploaded, See image is visible.

Expected behavior:

1. Uploaded image should be selectable if it matches filter (or should reset filter on tab change).

Current behavior:

1. Uploaded image after dirty filter is not selectable.

[utkarshpatel]

Screencast demonstrating bug

[hellofromTonya]

Hello @utkarshpatel,

Welcome back to WordPress Core's Trac 👋 Thank you for reporting this issue!

I can reproduce the issue on trunk, 5.8.3, and 5.5.8 (stopped testing at this point release). Investigation will be needed to identify when the bug was introduced and root cause. As I can reproduce, pulling it into the 6.0 milestone for further investigation.

As this is not due to 5.9, removing trunk as the Version. Once the version is identified, please update.

[utkarshpatel]

Hello @hellofromTonya,

Thank you!

I was able to reproduce the issue for version 5.0 - 5.4. This was introduced in 5.0 and 4.9 handles this correctly.

I will work on the patch.

[utkarshpatel]

Wrong test - was able to reproduce in WP version 4.6 - 5.4 as well.

[costdev]

After the discussion in the bug scrub, I'm moving this ticket to the 6.1 milestone, adding the needs-patch and has-testing-info keywords, and correcting a minor typo in the ticket title.

[antpb]

This one still needs a patch so might be better suited for 6.2. Moving to the next milestone but feel free to move it back if anyone has the bandwidth to make it happen for 6.1!

[Mista-Flo]

This is a tough one, the backbone app is quite hard to navigate, @adamsilverstein might be able to give some guidance here.

I tried to investigate but I'm a bit rusty inside the Media Library code to be honest.

[adeltahri]

I was able to reproduce the issue for the version of WordPress 6.2-alpha-54642

[antpb]

This is looking too much to land in 6.2 so we should move it to 6.3 asap.

[oglekler]

This ticket was discussed during the bug scrub. To help pinpoint the bug we agreed to check when this bug was firstly introduced.

Additional props: @mukesh27 @costdev

[oglekler]

This ticket was discussed during bug scrub and due to lack of patch and activity lately, it was decided to move in into 6.4.

Props @mukesh27

[nicolefurlan]

I've posted in #core-test to ask testers to help us pinpoint exactly when this bug was introduced.

[antpb]

Moving to 6.5 so we have more time to solve this.