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

View options: Distraction free is the only option to trigger a snackbar notice #66364

Closed
2 of 6 tasks
afercia opened this issue Oct 23, 2024 · 7 comments · Fixed by #66405
Closed
2 of 6 tasks

View options: Distraction free is the only option to trigger a snackbar notice #66364

afercia opened this issue Oct 23, 2024 · 7 comments · Fixed by #66405
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). l10n Localization and translations best practices [Package] Editor /packages/editor [Type] Bug An existing feature does not function as intended

Comments

@afercia
Copy link
Contributor

afercia commented Oct 23, 2024

Description

In the top bar 'Options' ellipsis menu, the first 4 options are related to 'view modes' of the editor:

  • Top toolbar
  • Distraction free
  • Spotlight mode
  • Fullscreen more

Image

The 'Distraction free' mode is the only one to trigger a snackbar notice. The other ones don't.

Image

The snackbar notice is a little unexpected to me. Also, not sure how the 'Undo' control in the notice is any valuable, given the Options menu is still open and users can just click again there to undo.

On top of that, activating and deactivating these options triggers an audible speak message for screen reader users. However, the message for distraction free mode is duplicated. Actually, two different components trigger a message for this same feature. Also, the wording of the message is inconsistent.

Screenshot when dumping all the speak messages to the console:

Image

Proposal

Either all these options should trigger a snackbar notice or none.
I'd like to propose to remove the snackbar notice of the Distraction free mode for consistency and simplicity. I'm not sure this snackbar notice adds much value.

Note: recommended to check what happens when toggling these options via the Command palette.

Step-by-step reproduction instructions

  • Edit a post.
  • Go to the top bar > Options.
  • Toggle on and off each view option.
  • Observe only Distraction free mode triggers a snackbar notice.

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

Please confirm which theme type you used for testing.

  • Block
  • Classic
  • Hybrid (e.g. classic with theme.json)
  • Not sure
@afercia afercia added [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Package] Editor /packages/editor [Type] Bug An existing feature does not function as intended l10n Localization and translations best practices labels Oct 23, 2024
@Vrishabhsk
Copy link
Contributor

Hi @afercia 👋

  • I have raised a PR addressing this : Fix : Snackbar Notice Inconsistency #66405
  • I went ahead and enabled all the View Options to show a Snackbar Notice
  • Since these options, when enabled via the Command Palette, show a notice, it only makes sense for them to show a notice when enabled via the More MenuView Options
  • It also provides a visual feedback to the user in case they are unfamiliar with the option and do not the state of the option

Let me know your thoughts on this. Thanks

@ntsekouras
Copy link
Contributor

To add some context, the snackbar was added for distraction free mode because it can be triggered in various conditions besides this toggle. We should definitely keep only one from the action.

So, if we want consistency @Vrishabhsk 's approach to add to the others is the way only way to go.

@mtias
Copy link
Member

mtias commented Oct 27, 2024

I don't think a notice is useful when triggered from the menu. Maybe the command palette should be the one triggering these.

@afercia
Copy link
Contributor Author

afercia commented Oct 28, 2024

I don't think a notice is useful when triggered from the menu. Maybe the command palette should be the one triggering these.

I'm not sure why the snackbar notice should sometimes appear and sometimes not for similar actions. I'm not sure that's any helpful from an user perspective. it may seem smart to contributors because we, as developers and designers, we know how these features work under the hood. However, to me, it doesn't make sense from an user perspective and it's just confusing.

Consistency is key. To me, these actions should either always trigger a notice or never.

@ntsekouras
Copy link
Contributor

I'm not sure why the snackbar notice should sometimes appear and sometimes not for similar actions.

This started with distraction free mode because it can be toggled based on other triggers and the user should be notified about the 'automated' change.

Consistency is key. To me, these actions should either always trigger a notice or never.

If all similar menu items don't trigger a notice can be considered consistent too and it makes sense.

@afercia
Copy link
Contributor Author

afercia commented Oct 30, 2024

If all similar menu items don't trigger a notice can be considered consistent too and it makes sense.

That's not the case. Activating Distraction free from the menu item does trigger a notice. Activating the other items, doesn't.

Image

@ntsekouras
Copy link
Contributor

That's not the case. Activating Distraction free from the menu item does trigger a notice. Activating the other items, doesn't.

Yeah, that's gonna be fixed in the linked PR.

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). l10n Localization and translations best practices [Package] Editor /packages/editor [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants