SOLVED IN 1.4: Text duplication in unit when adding a variable

[joa]

Bricks Version: 1.4.RC2
Browser: Firefox dev
OS: Windows
URL: https://screen.matriarch.ie/app/play/TdMx3DXi#g7hu9CuD

Trying to add a variable (from automatic.css) and having a weird duplication of the text. Was able to replicate it on several elements (screen recording above)

[timmse]

Hi Jo,
Thanks a lot for your report!

We are aware of the issue I recommend you not to use var, clamp, min, max, or anything else with brackets in the input fields.

SOLVED IN 1.4: Values with brackets (var, clamp, calc, etc.) in Input fields break styles

Version: 1.4RC2 Hi, It seems entering “(” anywhere in theme style not only breaks backend field, but it also breaks the whole stylesheet and whole website gets unstyled: [image] Note: I just entered “var(–titi)” in the field. Note 2: For existing var() and calc() in theme styling before 1.4RC2 upgrade, no problem, so it seems it’s only newly entered “(” that break everything. [image]

SOLVED IN 1.4: Bricks 1.4 RC2 - CSS Variables Not Working

Bricks Version: 1.4 RC2 Browser: MS Edge Version 101.0.1210.39 (Official build) (64-bit) OS: Windows 10 Home URL: Contact Us Left - Gerri Wiebe Adding CSS variables to padding fields doesn’t work. If you copy/paste the variable into the padding fields, the CSS variable is added twice like so: padding-top: var(–css-variable)var(–css-variable); If you type the variable name into the padding field, it appears like the value is added without a semicolon, which breaks the stylesheet. Here’s a…

SOLVED IN 1.4: Setting fields using "(" are broken in backend

Bricks Version: 1.4RC2 When using “(” symbol (like with var and calc) in margins/paddings: width auto is used for unit string and breaks design (you have to scroll to see all section) actual input field disappears and we can’t do anything to get it back [image]

Cheers,
timmse

[joa]

Thanks @timmse! I searched the forum but wasn’t searching for the right words

[ChrisCastillo]

Hey Stefan, was this fixed in the stable 1.4 release?

[timmse]

Yes @ChrisCastillo . The problem that can occur now is that the values (var, clamp, calc etc) must be re-entered and saved, since they were unfortunately also written incorrectly to the database possibly breaking the styles that follow.

This is for example a result of it: SOLVED: Broken layout on the front

[timmse]

Hi Jo,
The issue has been fixed with Bricks 1.4.
The only problem that may occur now is that the broken variables (or functions) have been stored in the database and therefore do not work anymore.

So if you run into a broken layout somewhere, it is most likely due to a broken value in an input field like “var(var(–variable)”. Sorry for the trouble.

Best regards,
timmse