After Gutenberg 18.9.0 was pushed to WoA, some customers are reporting that the editor hangs/fails to load when trying to create or modify a page or post.
I haven't been able to reproduce the issue on my end, but the 2 customers who reported it noted that the editor was hanging consistently, and then the issue was resolved when Gutenberg was deactivated. I noted a short delay for the editor to load, during which I noted this error in the console:
chromewebdata/:1 Refused to display '{domain}' in a frame because it set 'X-Frame-Options' to 'deny'.
This issue was escalated and intermittently reproduced by @obenland. Discussion here: p1723150860104919-slack-C02FMH4G8
Steps to reproduce
Ensure Gutenberg 18.9.0 is activated on a WoA site
Attempt to create or modify a page or post
What you expected to happen
The editor should not hang or fail to load
What actually happened
The editor fails to load
Impact
Some (< 50%)
Available workarounds?
Yes, easy to implement
If the above answer is "Yes...", outline the workaround.
Quick summary
After Gutenberg 18.9.0 was pushed to WoA, some customers are reporting that the editor hangs/fails to load when trying to create or modify a page or post.
I haven't been able to reproduce the issue on my end, but the 2 customers who reported it noted that the editor was hanging consistently, and then the issue was resolved when Gutenberg was deactivated. I noted a short delay for the editor to load, during which I noted this error in the console:
This issue was escalated and intermittently reproduced by @obenland. Discussion here: p1723150860104919-slack-C02FMH4G8
Steps to reproduce
What you expected to happen
The editor should not hang or fail to load
What actually happened
The editor fails to load
Impact
Some (< 50%)
Available workarounds?
Yes, easy to implement
If the above answer is "Yes...", outline the workaround.
Deactivating Gutenberg resolves the issue.
Platform (Simple and/or Atomic)
Atomic
Logs or notes
No response