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: jorgefilipecosta <jorgefilipecosta@git.wordpress.org>
Co-authored-by: jameskoster <jameskoster@git.wordpress.org>
Co-authored-by: tyxla <tyxla@git.wordpress.org>
Co-authored-by: mtias <matveb@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: -49 B (0%)

Total Size: 2.2 MB

_{compressed-size-action}

I'll review in detail later today, but curious why the spacing between buttons are different in this screenshot?

I'll review in detail later today, but curious why the spacing between buttons are different in this screenshot?

I'm sorry, I changed the styles, a little bit and some of the screenshots used the old ones by mistake, I updated all screenshots. I'm not totally sure about which spacing is better but I'm open to any change there.

I pushed some small changes:

• Removed component style overrides.
• We shouldn't use the link variant because it adds an underline which is misleading (these aren't links).
• I used the default variant for stylistic coherence with the ... button.
• Reduced gap between buttons to 0.

The mobile experience is very awkward. We could switch to icon buttons, but I'm not sure it's worth it because as we add more actions in the future it's going to be very difficult to find icons to represent them all. On balance it might be simpler to hide primary actions on mobile (they're still accessible in the ... menu).

Acknowledgements/follow-ups

• The visual gap between buttons is still too large, but this is as far as we can go without overriding component styles which is something I'd really like to avoid. It would be neat to have an 'unstyled' button variant for situations like this (cc @aduth).
• The row of actions on the Pages DataView is quite long... Depending on i18n we can potentially simplify the 'Move to trash' action to just 'Trash' which would help a bit.

@tyxla what is going on with the ... button there? I don't see that 🤔

@tyxla what is going on with the ... button there? I don't see that 🤔

Yeah, felt wrong to me too so I debugged. Looks like I had some plugins messing with the styles. It looks alright now, so no need to do anything there:

The mobile experience is very awkward. We could switch to icon buttons, but I'm not sure it's worth it because as we add more actions in the future it's going to be very difficult to find icons to represent them all. On balance it might be simpler to hide primary actions on mobile (they're still accessible in the ... menu).

Agreed it is not that the actions look wrong but they take most of the space so other data becomes invisible. Moving the primary actions to the actions menu on mobile seems a good option to me. I will give it a try.

The row of actions on the Pages DataView is quite long... Depending on i18n we can potentially simplify the 'Move to trash' action to just 'Trash' which would help a bit.

That seems a simple improvement that could work well for some langua users and It is a simple change we can add.

Moving the primary actions to the actions menu

I think they're already there, so it's just a case of hiding primary actions on mobile.

By the way, this should also reflect on the bulk editing footer actions area.

Flaky tests detected in 47a8c49.
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/18648872692
📝 Reported issues:

• [Flaky Test] ensures List View global shortcut works properly #51533 in /test/e2e/specs/editor/various/list-view.spec.js

Following up with the bulk actions change.

Very small PR at #72501 (I was not expecting things to work right away and for the PR to be so small, otherwise I would have had included the changes here) cc: @jameskoster.

Cherry-picked to the wp/latest branch to include it in WordPress 6.9 Beta1 in 7d0076f

I just cherry-picked this PR to the release/21.9 branch to get it included in the next release: 265e662