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

Top editing bar inaccessible with Distraction-Free mode enabled in Site Editor #91739

Closed
cuemarie opened this issue Jun 12, 2024 · 5 comments
Closed
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Full Site Editor The site editor. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Platform] Atomic [Platform] Simple [Pri] Normal [Product] WordPress.com All features accessible on and related to WordPress.com. [Type] Bug

Comments

@cuemarie
Copy link

Quick summary

When you enable Distraction-Free mode in the page/post editor, you can access the top editing bar tools (including the options menu to disable it again) by hovering at the top of the page.

In the Site Editor, the top bar does not reappear when you hover at the top of the editor, making it difficult to exit distraction-free mode or use any tools.

Steps to reproduce

  1. Open Site Editor > Template
  2. Options > Enable Distraction-Free mode
  3. hover near top of page

What you expected to happen

CleanShot 2024-06-12 at 15 48 17

What actually happened

CleanShot 2024-06-12 at 15 50 54

Impact

Most (> 50%)

Available workarounds?

Yes, easy to implement

Platform (Simple and/or Atomic)

Simple, Atomic

Logs or notes

Workarounds: Shortcuts (CTRL + Shift + \ on Windows, and SHIFT + COMMAND + \ on MacOS) work in the meantime, or exiting the editor to browse mode, then re-entering the template

Customer report: 8322202-zen

@cuemarie cuemarie added [Type] Bug Needs triage Ticket needs to be triaged [Feature] Full Site Editor The site editor. [Product] WordPress.com All features accessible on and related to WordPress.com. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. labels Jun 12, 2024
Copy link

Support References

This comment is automatically generated. Please do not edit it.

  • 8322202-zen

@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". label Jun 12, 2024
@mrfoxtalbot
Copy link

I can replicate this and I can confirm it is NOT happening on a self-hosted site.

Could someone from @Automattic/lego help us triage this? Thank you!

@mrfoxtalbot mrfoxtalbot removed the Needs triage Ticket needs to be triaged label Jun 19, 2024
@taipeicoder
Copy link
Contributor

taipeicoder commented Jun 20, 2024

Thanks for the ping @mrfoxtalbot!
I can reproduce this on my end. Let me add this to the Lego backlog and triage this.

@taipeicoder
Copy link
Contributor

taipeicoder commented Jun 21, 2024

@mrfoxtalbot I was able to reproduce this issue with a JN running Gutenberg 18.5. Upgrading to 18.6 fixes this issue, I verified it on an Atomic site.

Could you confirm if upgrading Gutenberg to 18.6 fixes this issue?

@mrfoxtalbot
Copy link

It does, thank you!

Kapture.2024-06-21.at.12.33.57.mp4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Full Site Editor The site editor. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Platform] Atomic [Platform] Simple [Pri] Normal [Product] WordPress.com All features accessible on and related to WordPress.com. [Type] Bug
Development

No branches or pull requests

3 participants