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: t-hamano <wildworks@git.wordpress.org>
Co-authored-by: juanfra <juanfra@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Size Change: +6 B (0%)

Total Size: 1.84 MB

_{compressed-size-action}

Thanks for the review!

I'm wondering if we should do the same for the other resets we've implemented, for consistency. Although there's more than one "reset" options on those cases.

Yes, I think we need to. For example, the reset button added by #67116 is not touchable on devices that don't support hover. The "Clear" button is available in the dropdown, but it may be better to always show the reset button, as in this PR.

Flaky tests detected in b41852a.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/12408743322
📝 Reported issues:

• [Flaky Test] Navigates the items list via UP/DOWN arrow keys #64334 in /test/e2e/specs/site-editor/dataviews-list-layout-keyboard.spec.js
• [Flaky Test] submenu click on the arrow interactions #61884 in /test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js

Thanks for the work on this 👍 LGTM!

The "Clear" button is available in the dropdown, but it may be better to always show the reset button, as in this PR.

That was my thought. I'll adapt the other reset to get this fixed. Thank you 🙏