Do we think that having two places to add filters is a good idea? Why can't we just remove the filters from the table headers (no other view outside table allows this inline filtering)

I think it's quite handy, as are the other actions in that menu (re-ordering, hiding).

Other actions like pinning (#64679) could be contained here in the future. Thinking about custom fields you might also be able to rename, or go and edit other field properties from this menu.

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: @raj.patel@rtcamp.com.

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: raj.patel@rtcamp.com.

Co-authored-by: jorgefilipecosta <jorgefilipecosta@git.wordpress.org>
Co-authored-by: youknowriad <youknowriad@git.wordpress.org>
Co-authored-by: jameskoster <jameskoster@git.wordpress.org>
Co-authored-by: imrraaj <imrraaj@git.wordpress.org>
Co-authored-by: oandregal <oandregal@git.wordpress.org>

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

Hey @jameskoster, Can you please review the PR?

@imrraaj this one needs a code review from someone like @youknowriad or @jorgefilipecosta.

Interestingly, it works in the storybook (where DataViews is a standalone component), so I wonder if there's some edit-site code that is preventing this from working in the site editor:

@jameskoster, would the change I described above be something we are ok with? Or is it something we want to avoid?

@jorgefilipecosta Ideally the bundled views all behave the same in this respect.

• In the Pages page filters are hidden entirely when browsing by status.
• In the Patterns page filters are hidden entirely when browsing by category.
• In the Templates page, filters are hidden by default but still accessible when browsing by author.

As we can see Templates are the odd one out. But this is an issue on trunk, so we don't necessarily have to fix it here. What do you think?

Thanks for the PR! I'm closing though since this has been resolved for a while and I closed the linked issue too.