DataViews table layout: hide actions menu when there is only one action and is primary

[oandregal]

Part of #65165

What?

This PR hides the actions menu for the DataViews table layout when there's only 1 action and is primary.

Before	After

All current core screens have more than one action. See testing instructions below.

Why?

To improve UX.

Testing Instructions

This is something we've heard from extenders. Because there's no place in core where we have this situation just yet, we have to create one for testing:

• Go to the post-list code and remove the postTypeActions in this line and in the line below (in both arrays).
• Visit the Pages page and switch to the table layout.
• Verify the actions menu is hidden, only the edit icon is displayed.

[github-actions]

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: oandregal <[email protected]>
Co-authored-by: Mamaduka <[email protected]>
Co-authored-by: ntsekouras <[email protected]>

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

[Mamaduka]

Works as advertised ✅

[ntsekouras]

Why not inline the check?

[oandregal]

That could work as well. No big feelings either way. I suppose I thought it better to have it explain the why.

[ntsekouras]

Noting that we do this for every layout and not only for table. We should update the title.

I was a bit confused that list layout doesn't use these action components. It seems probably about adding some extra things for keyboard navigation and I'm wondering if we can absorb that somehow.

[oandregal]

Noting that we do this for every layout and not only for table. We should update the title.

This is actually only for the table. Here's the PR for the list #67015 :)

The list view uses the subcomponents directly to handle the keyboard interactions. The grid is unaffected because it uses the compact view (no primary actions visible). This can be tested by switching to any other layout during testing.

List	Grid	Table

[ntsekouras]

The list view uses the subcomponents directly to handle the keyboard interactions. The grid is unaffected because it uses the compact view (no primary actions visible). This can be tested by switching to any other layout during testing.

Exactly. If grid wasn't using the compact and had one primary action would have the same behavior. For now it doesn't, but when we open the API for registering layouts, this behavior will be for any layout.

[oandregal]

@ntsekouras Agreed. If things worked differently then yes, it'd make sense to change the changelog/issue title to be about all the layouts. I just worry that it'd be confusing to say so when it's not true right now? Not sure how it could be improved without being confusing, but happy to explore alternatives if you have any suggestion.

[ntsekouras]

The title is not that important right now, yes. We should keep this in mind when creating the API for layouts to document it.