Don't force users to move their mouse when publishing #65315
Labels
[Focus] Accessibility (a11y)
Changes that impact accessibility and need corresponding review (e.g. markup changes).
Needs Design Feedback
Needs general design feedback.
[Package] Edit Post
/packages/edit-post
[Status] In Progress
Tracking issues with work in progress
[Type] Bug
An existing feature does not function as intended
Description
One small annoyance that always bugged me personally is that when publishing a post I have to move my mouse (or any other pointing device I may be using) to click the second 'Publish' button in the pre-publish checks panel.
The pre-publish checks are enabled by default and publishing a post is a twe-step process:
As a user, I would love to just click again and not be forced to move my mouse.
Also, the placement of the Publish / Cancel buttons in the pre-publish checks panel is inconsistent with the convention used in many other places in the editor. For example, all modal dialogs, confirm dialogs etc. place Cancel first and OK / Submit second.
This is a long standing annoyance but after the change in #65163 it's slightly worse. The Publish button in the top bar has been moved slightly to the right. I agree it's an improvement as the button is now in a more predictable place and not influenced by potential presence of plugins toggle buttons. However, users have to move their mouse over a longer distance to be able to click the second Publish button.
An easy win could be to just swap the position of the two buttons in the pre-publish checks panel.
Worth reminding the actual buttons length and distance may vary depending on the admin language, as languages other than English may provide longer / shorter translations.
Animated GIF to illustrate:
Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
No response
Environment info
No response
Please confirm that you have searched existing issues in the repo.
Please confirm that you have tested with all plugins deactivated except Gutenberg.
The text was updated successfully, but these errors were encountered: