Hey @Norm
I think it would be handy, it the slider in the Bric Builder, could be restricted to whole numbers (as an option). I know we can round up/down the value in js, but it would make the slider less sensitive I think.
![]()
Hey @Norm
I think it would be handy, it the slider in the Bric Builder, could be restricted to whole numbers (as an option). I know we can round up/down the value in js, but it would make the slider less sensitive I think.
![]()
That may be the cause, is it being loaded within the Brics HTML?
It was temporary dumped into a code widget on the canvas, so yeah.
Preview was off.
First time this has happened though.
Custom JS loaded into the design environment can cause this type of reloading, the design canvas is basically a safari browser and JS can ask the browser to reload and refresh that kind of stuff.
Really, even with just a js library. wow.
Granted, I seldom do it this way, only when I am trying something out quickly.
Depends what the JS library is doing and if you can get it out of the sandbox and into the design canvas environment without it being picked up by Blocs.
Hi @norm,
The class manager currently changes a class names to lowercase letters even though the specified class was typed with some lower case letters. Classes are case sensitive:
For example if I was changing the attributes of a class from a vendor named:
containerBackground
If I type containerBackground in the class manager it creates a class called containerbackground, which then it does not work with the vendor’s class named containerBackground.
So the only way to change the attributes of that class is to created in the Code Editor.
Yeah this has always been the case classes are all made lowercase.
Moving forward can that behavior be changed?
Many of the plug-ins classes use names with uppercase letters. Ecwid for example is one. So, if I need to add an Ecwid class to the class manager it doesn’t work.
Its unlikely to happen in 5.2.
in 5.2.1 ? ![]()
No, it’s a big change that effects a large portion of the app as classes are always expected to be lowercase and would need a lot of testing. So It’s more likely to come (if there is enough demand) in a major update that has been tested for 5 to 6 months.
And what is needed to have auto scroll?
unless its added, you will need to write some javascript.
I remember mentioning the absence of camelCase back in early 2018 (maybe even further back on the old forum), that would of allowed 5 years for testing. ![]()