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: History Shows Black Screen When Page Has Unsupported Block #15779

Open
theck13 opened this issue Dec 29, 2021 · 0 comments
Open

Editor: History Shows Black Screen When Page Has Unsupported Block #15779

theck13 opened this issue Dec 29, 2021 · 0 comments
Labels
Gutenberg Editing and display of Gutenberg blocks. [Pri] Medium [Type] Bug

Comments

@theck13
Copy link
Contributor

theck13 commented Dec 29, 2021

Expected

Pages with an unsupported block show a dialog or an error when viewing history. Ideally, history would still be viewable even with pages with an unsupported block.

Observed

Pages with an unsupported block show a black screen and crash when viewing history. On a real device, the black screen is shown indefinitely. On an emulated device, the black screen is shown momentarily then the Pages screen is shown. See the animation below for illustration.

Reproduced

  1. Tap My Site tab in bottom navigation.
  2. Tap Pages item under Publish section.
  3. Notice Pages screen is shown.
  4. Tap any page with unsupported block.
  5. Tap ellipsis/overflow action in app bar.
  6. Tap History item in menu.
  7. Tap any history item in list.
  8. Notice black screen and crash.
  9. Notice Pages screen is shown.
Tested

Google Pixel 5 on Android 11.0.0 with WordPress 18.9-rc-1
Google Pixel 2 on Android 10.0.0 with WordPress 18.9-rc-1

@dcalhoun dcalhoun added Gutenberg Editing and display of Gutenberg blocks. and removed gutenberg-mobile labels Apr 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Gutenberg Editing and display of Gutenberg blocks. [Pri] Medium [Type] Bug
Projects
None yet
Development

No branches or pull requests

3 participants