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

Editor > Pages: It is impossible to access the editor on mobile #90614

Closed
mrfoxtalbot opened this issue May 11, 2024 · 1 comment
Closed

Editor > Pages: It is impossible to access the editor on mobile #90614

mrfoxtalbot opened this issue May 11, 2024 · 1 comment
Labels
[Feature] Full Site Editor The site editor. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Platform] Atomic [Platform] Simple [Pri] High Address as soon as possible after BLOCKER issues [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts Triaged To be used when issues have been triaged. [Type] Bug

Comments

@mrfoxtalbot
Copy link

mrfoxtalbot commented May 11, 2024

This is a tracking issue, it needs to be fixed upstream in WordPress/gutenberg#61555

Description

On mobile, the Page List gets stuck in the "select page" step.

Kapture.2024-05-10.at.07.25.27.mp4

I expected this section to disappear as soon as I select one of the pages but it does not.

The desktop version relies on the user clicking on the page's content to edit but this is simple not possible mobile because the page preview is not available.

Step-by-step reproduction instructions

  1. Using a narrow viewport, got to Appearance > Editor > Pages
  2. Select a page
  3. Notice how the page itself is not opened in the editor.

Screenshots, screen recording, code snippet

No response

Environment info

  • WordPress 6.5.3 running Twenty Twenty-Four
  • Gutenberg version 18.3.0
  • No plugins

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

Steps to reproduce

.

What you expected to happen

.

What actually happened

.

Impact

All

Available workarounds?

Yes, difficult to implement

Platform (Simple and/or Atomic)

Simple, Atomic

Logs or notes

No response

@mrfoxtalbot mrfoxtalbot 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 May 11, 2024
@github-actions github-actions bot added the [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts label May 11, 2024
@mrfoxtalbot mrfoxtalbot moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ May 11, 2024
@mrfoxtalbot mrfoxtalbot added Triaged To be used when issues have been triaged. and removed Needs triage Ticket needs to be triaged labels May 11, 2024
@github-actions github-actions bot added [Platform] Atomic [Platform] Simple [Pri] High Address as soon as possible after BLOCKER issues labels May 11, 2024
@mrfoxtalbot
Copy link
Author

Fixed by WordPress/gutenberg#60805

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Full Site Editor The site editor. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Platform] Atomic [Platform] Simple [Pri] High Address as soon as possible after BLOCKER issues [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts Triaged To be used when issues have been triaged. [Type] Bug
Development

No branches or pull requests

1 participant