SOLVED: Custom CSS Tab doesn't display the full code and jumps

Bugs
1

Win 11, Chrome and Brave. Unable to attach video as your forum doesnt allow me to do so.

2

3

Hi @primexaos,

please use https://jam.dev/ or some similar service. Having a video and a way to replicate this would be great :slight_smile:

Matej

4

Here is the video link - half of the code is hidden.

5

Here is Google Drive public link. It should not require age verification.

6

Hi @primexaos,

for this video, I was actually able to watch it. I am not sure why the other one was different.

Anyway, I could replicate the issue, and I’ve added it to our internal bug tracker. Can you just confirm if I got it right:

  • When switching from the Style to the Content tab, and resizing the “Custom CSS” control, the CSS will be cut off
  • As soon as you scroll it, it will show.

Am I missing anything else?
Matej

7
  1. yes, but not just resizing. half of the code is cut off all the time.
  2. no, it will not show on scroll, it shows only when you click on the hidden code or if the blinking KB cursor touches the hidden code. it will not show if you click on the first part of the code. the problem is that you resize the window, the code is NOT shown, and you dont know that you should click on the empty space in order to reveal the code, meaning you look at the code, you think its only 5 lines, and end up having a lot of issues trying to determine whats wrong with your css.
8

Hi @primexaos,

what do you mean “all the time”? If you don’t resize the “Custom CSS” window, and only scroll, it shows all code (see your video at around 7s).

Ok, so in your case, if you click on the hidden code. I have not tested it, but I will add it to the task.
So, instead of clicking, if you try to scroll, is it not working for you? Not resize - I understand that.

Matej

9

Oh, thats what you meant… Scrolling reveals the full code, resizing does not, right?

10

Exactly :victory_hand:

1 Like
11

We’ve addressed this in Bricks 2.3.5, 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.

1 Like