DataViews: Avoid unselecting items that are not rendered#70572
DataViews: Avoid unselecting items that are not rendered#70572youknowriad wants to merge 1 commit intotrunkfrom
Conversation
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Size Change: -66 B (0%) Total Size: 1.87 MB
ℹ️ View Unchanged
|
|
I can confirm that this fixes deselection when searching the items. I also noticed that it introduces a regression when the selected item is moved to the trash. Previously, it would load the homepage after the deletion; now it will display a warning in the canvas. Not sure if this is intentional now. ScreencastCleanShot.2025-07-03.at.18.20.18.mp4 |
|
Not sure how relevant is this still. We can resurface it if it comes up again. |
What?
In the pages dataviews, when you select an item and then search for something unrelated, the preview changes back to the front page. For me is this the wrong behavior and the previous selection should be kept unless the user changes it explicitly.
Testing Instructions