Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't force users to move their mouse when publishing #65315

Closed
2 tasks done
afercia opened this issue Sep 13, 2024 · 0 comments · Fixed by #65317
Closed
2 tasks done

Don't force users to move their mouse when publishing #65315

afercia opened this issue Sep 13, 2024 · 0 comments · Fixed by #65317
Assignees
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

Comments

@afercia
Copy link
Contributor

afercia commented Sep 13, 2024

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:

  • Click Publish in the top bar.
  • The pre-publish checks panel appears.
  • Click Publish in the panel.

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:

flying buttons

Step-by-step reproduction instructions

  • Create a new post.
  • Enter some content.
  • Make sure the Pre-publish checks are enabled in the editor preferences.
  • Click Publish in the editor top bar.
  • The Pre-publish checks panel appears.
  • Observe that at this point under your mouse there's the Cancel button.
  • Observe that to click the second Publish button you have to move your mouse.

Screenshots, screen recording, code snippet

No response

Environment info

No response

Please confirm that you have searched existing issues in the repo.

  • Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

  • Yes
@afercia afercia added [Type] Bug An existing feature does not function as intended [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 labels Sep 13, 2024
@afercia afercia self-assigned this Sep 13, 2024
@github-actions github-actions bot added the [Status] In Progress Tracking issues with work in progress label Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant