Bricks Version: 1.7
When you have a long code in the Code Element requiring scrolling, and you make a mistake and click on Ctrl+Z, the Code Element’s scroll bar takes you all the way back up at the beginning and ‘appends’ the previous edits with the ‘mistake’ code. You have to scroll back down to where you were and weed out the ‘wrong’ code.
This also happens to me and hate it lol. I try to refrain from cmd + z, but sometimes second-nature takes its course.
Please fix Bricks’ team!
Thanks so much for your report!
I was able to reproduce the scrolling up issue, but I’m not sure what you mean by " ‘appends’ the previous edits with the ‘mistake’ code". Can you record a short video about this?
Hey Timimy, thanks for the reply.
Here is a video: Watch video Bricks bug - share-me.video
You can see I type
timer2+=2;, save, and then press Ctrl+Z 4 times. It completely goes away on the 4th attempt otherwise some artifacts remain.
Thanks for the video!
With birdeatsbug or jam.dev it would still have been better because there every one of your inputs is logged, so we can specifically track what you pressed and when
I see the problem and add it to the bug tracker.
Timmy, I tried to use birdeatsbug and jam.dev but looks like they are Chrome exclusives. and I do all the development on Firefox. All my passwords are mess to remember so I didnt go that route at this time. But I will try to use them for every consequent request here
I also don’t understand why the cursor always scrolls back to the top in any code blocks (advanced page settings, code blocks widget, or template settings). Maybe it is a Mac and/or Firefox issue? Not sure.
I discovered this as well…if you type Cmd-z, the previously removed css is added back twice inn 1.9.
yes. this does happen. The previous state also shows.
We’ve fixed this issue in Bricks 1.9.2, now available as a one-click update in your WordPress Dashboard.
Changelog: Changelog – Bricks
Please let us know if you are still experiencing issues.
I updated and I can confirm I am no longer experiencing that issue. Thank you.
@timmse thanks a lot you guys.