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.

Sign up for GitHub

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

Jump to bottom

Site Editor is empty in Firefox #28403

Closed
Sandstromer opened this issue Jan 21, 2021 · 11 comments
Closed

Site Editor is empty in Firefox #28403

Sandstromer opened this issue Jan 21, 2021 · 11 comments
Labels
Browser Issues Issues or PRs that are related to browser specific problems Needs Testing Needs further testing to be confirmed. [Priority] High Used to indicate top priority items that need quick attention [Type] Bug An existing feature does not function as intended

Comments

@Sandstromer
Copy link

Description

Since 9.8.0 the Site Editor is empty when using Firefox browser.
Other browsers that I have tested (Chrome & Edge) not affected, although now much slower to load when compared to previous version of Gutenberg.

Step-by-step reproduction instructions

  1. In the dashboard, click on 'Site Editor (beta)'

Expected behaviour

Load the Site Editor.

Actual behaviour

The Site Editor does not load, and is an empty grey page, then redirects to standard dashboard type layout with empty page.

Screenshots or screen recording (optional)

site-editor-blank

site-editor-blank-redirect

WordPress information

  • WordPress version: 5.6
  • Gutenberg version: 9.8.0
  • Are all plugins except Gutenberg deactivated? Yes
  • Are you using a default theme (e.g. Twenty Twenty-One)? No (using 'TT1 Blocks' theme)

Device information

  • Device: Desktop
  • Operating system: Windows 10
  • Browser: Firefox 84.0.2
@Sandstromer
Copy link
Author

Console errors if it helps.

/gutenberg/vendor/react-dom.min.de439aae.js:125:24

TypeError: n is undefined
Vp /wp-content/plugins/gutenberg/build/block-editor/index.js?ver=1cd322178bcb34cc86341ccc8d0e3ed5:81
Bh /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:126
Dj /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:162
unstable_runWithPriority /wp-content/plugins/gutenberg/vendor/react.min.e713ea3b.js:25
Da /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:60
xb /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:162
Te /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:146
Pg /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:61
unstable_runWithPriority /wp-content/plugins/gutenberg/vendor/react.min.e713ea3b.js:25
Da /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:60
Pg /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:61
ha /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:60
Ja /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:224
ch /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:93
t /wp-content/plugins/gutenberg/build/block-editor/index.js?ver=1cd322178bcb34cc86341ccc8d0e3ed5:81
b /wp-content/plugins/gutenberg/build/block-editor/index.js?ver=1cd322178bcb34cc86341ccc8d0e3ed5:81

/gutenberg/build/block-editor/index.js:81:23058

Uncaught TypeError: n is undefined
Vp /wp-content/plugins/gutenberg/build/block-editor/index.js?ver=1cd322178bcb34cc86341ccc8d0e3ed5:81
Bh /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:126
Dj /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:162
unstable_runWithPriority /wp-content/plugins/gutenberg/vendor/react.min.e713ea3b.js:25
Da /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:60
xb /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:162
Te /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:146
Pg /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:61
unstable_runWithPriority /wp-content/plugins/gutenberg/vendor/react.min.e713ea3b.js:25
Da /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:60
Pg /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:61
ha /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:60
Ja /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:224
ch /wp-content/plugins/gutenberg/vendor/react-dom.min.de439aae.js:93
t /wp-content/plugins/gutenberg/build/block-editor/index.js?ver=1cd322178bcb34cc86341ccc8d0e3ed5:81
b /wp-content/plugins/gutenberg/build/block-editor/index.js?ver=1cd322178bcb34cc86341ccc8d0e3ed5:81

@gziolo gziolo added [Type] Bug An existing feature does not function as intended Browser Issues Issues or PRs that are related to browser specific problems labels Jan 22, 2021
@gziolo
Copy link
Member

gziolo commented Jan 22, 2021 •
edited
Loading

It was also mentioned in the comment on WP Tavern: https://wptavern.com/gutenberg-9-8-brings-rounded-borders-to-the-group-block-and-moves-the-site-editor-canvas-into-an-inline-frame#comment-361459
#28403

@WordPress/gutenberg-core

@gziolo gziolo added [Priority] High Used to indicate top priority items that need quick attention Needs Testing Needs further testing to be confirmed. labels Jan 22, 2021
@carolinan
Copy link
Contributor

Hi
I am able to reproduce this with full site editing themes that still has the theme attribute ("theme":"tt1-blocks") for the template parts.

I am not able to reproduce it with themes that have had the theme attribute removed in preparation for version 9.9 (#28088)

@aristath
Copy link
Member

Just a note in case it's related: There was an error initially with iFrames and Firefox which was fixed in #28212.
I don't think it was included in v9.8, if not it will be included in v9.9

@ntsekouras
Copy link
Contributor

I don't think it was included in v9.8, if not it will be included in v9.9

It was not included. It works with the fix @aristath mentioned.

@aristath
Copy link
Member

aristath commented Jan 22, 2021 •
edited
Loading

Thank you for verifying @ntsekouras
In that case I'm closing this one as it has already been fixed and I can confirm everything works fine using the master branch.
Duplicate of #28212

@ockham
Copy link
Contributor

ockham commented Jan 22, 2021

I've cherry-picked the relevant commit to the release/9.8 branch and will include it in 9.8.1 (to be released later today).

@Sandstromer
Copy link
Author

9.8.1 mostly fixes this issue.

Occasionally the site editor hangs with the grey screen, and gives this console error:
Uncaught (in promise) SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data

Forcing a refresh (sometimes once, sometimes twice is needed) usually corrects it.

@TechDotHaus
Copy link

TechDotHaus commented Aug 18, 2021 •
edited
Loading

I am having this same issue as shown in the original screenshots using:
WordPress 5.8 running blockbase or quadrat using Gutenberg plugin 11.2.1

This happens both on Firefox and Firefox Developer Edition, locally, and on my server.

Can this be reopened?

@ntsekouras
Copy link
Contributor

@TechDotHaus can you try GB 11.3? I think there was a new similar WSOD that was fixed in this PR: #33896

@TechDotHaus
Copy link

@TechDotHaus can you try GB 11.3? I think there was a new similar WSOD that was fixed in this PR: #33896

Thank you. All clear :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Browser Issues Issues or PRs that are related to browser specific problems Needs Testing Needs further testing to be confirmed. [Priority] High Used to indicate top priority items that need quick attention [Type] Bug An existing feature does not function as intended
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@ockham @aristath @gziolo @TechDotHaus @carolinan @ntsekouras @Sandstromer