SOLVED IN 1.4: Adding CLAMP formula breaks control panel layout

[timmse]

Hi Michael,
Thanks a lot for your report, but…

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]

I would recommend you in 1.4RC2 not to use var, clamp, min, max or anything else with brackets in the input fields.

Cheers,
timmse