SOLVED: Custom CSS editor becomes unresponsive after 2.3.5 update

Browser: Chrome 148 / FF 150
OS: macOS
Video: https://drive.google.com/file/d/1iHPS9fqueLyQ8MvhJNUHhPU6kC2zc6dv/view?usp=sharing

Since updating to 2.3.5, the Custom CSS editor inside elements randomly becomes unresponsive. Clicking inside it and typing does nothing. I tested another site on 2.3.4 before updating it and had no issues. The problem presented itself after updating that site to 2.3.5.

Steps to reproduce

  1. Open any element’s settings
  2. Go to the Custom CSS tab
  3. Click inside the editor and try to type
  4. The editor does not respond

Workaround: Clicking the fullscreen or collapse icon on the editor temporarily fixes it, but the problem comes back after a short while.

2 Likes

Hey @eiacatki,

I can’t replicate this issue on my own local 2.3.5 install. What happens if you downgrade to 2.3.4? Does it start working?

Can you also replicate the issue on try.bricksbuilder.io?

Best regards,
Matej

Hi Matej

I have several installs I’ve updated to 2.3.5 and all of them exhibit this issue - Different hosts, plugins etc. All were fine on 2.3.4. I can also replicate it on try.bricksbuilder.io in both Chrome incognito and Firefox private browsing.

The only pattern I’ve identified is that it seems to occur when the CSS in the editor exceeds around 10 lines. Anything under that appears to work fine, which seems bizarre.

Also, clicking around the box when the issue exhibits itself throws this recurring error in the console: Uncaught TypeError: can’t access property “map”, r is undefined

Hey @eiacatki,

Thank you for the additional details. I was able to replicate the issue even in our latest development branch, and I also found the reason why this is occurring. It stems from adding the ResizableObserver to the CodeMirror instance as part of another fix. I have created a local task to address this and will let you know once it is resolved.

It appears this behavior only happens when the code element is resized. We will need to determine a solution for this or revert to the previous behavior. However, I believe it will be addressed in the next update.

Thank you.
Matej

It seems to be unresponsive the moment you alter the textarea height. If you click somehwere outsite and return back the textarea reset it’s size and working again.

1 Like

We’ve addressed this in Bricks 2.3.6, now available as a one-click update in your WordPress Dashboard.

Please read the changelog entry before updating, and let us know if you experience any issues.