search

WordPress / gutenberg

The Block Editor project for WordPress and beyond. Plugin is available from the official repository.
https://wordpress.org/gutenberg/
Other
10.49k stars 4.18k forks source link

Decreased performance when using theme editor styles and Custom HTML block #27785

Closed nk-o closed 3 years ago

nk-o commented 3 years ago

When we use styles for an editor from the theme and insert a Custom HTML block in any page, we will see the performance decrease while typing.

The problem is also visible with the default Twenty Twenty One theme. I have added more CSS (20k lines) to see more performance decrease for testing purposes.

To reproduce Steps to reproduce the behavior:

  1. Install and activate the theme with editor styles - https://github.com/nk-o/test-gutenberg-custom-html-block-performance
  2. Open any page and insert Custom HTML to the editor
  3. Try to type something inside it
  4. See how freezing editor

Screenshots I just type "Test" in the Custom HTML block. See on the screenshot how the Perforformance Chrome tab looks like:

image

Editor version (please complete the following information):

Desktop (please complete the following information):

maddisondesigns commented 3 years ago

I'm also finding that as soon as you insert a Custom HTML Block into your page, the whole page performance slows down, and it becomes very sluggish when typing or even just trying to select other blocks.

mwidmann commented 3 years ago

Our users have reported the same issue. Seems to be a new thing happening since updating to WP5.6. Haven't tried installing the Gutenberg Plugin.

Seems to occur in every browser, operating system we tried it on.

mwidmann commented 3 years ago

Just tested with WP 5.6.1 and the issue isn't resolved. Tried it out in WP 5.7 beta 1 and there the issue doesn't occur. Either this release uses an older version of Gutenberg (which I hope isn't the case as that would mean this bug is going to be ported to 5.7 eventually, or it has been fixed downstream.

At first I thought that this could possibly be related to this fixed bug in Core, but this didn't solve the problem.

So far our only option is to stay on 5.5.3 until this is resolved.

mwidmann commented 3 years ago

As a follow up. I just tested it with the freshly released WordPress 5.7 and the issue seems to be gone.

skorasaurus commented 3 years ago

Thanks for following up @mwidmann.

Please reopen if you're you still experiencing this issue.