Hi I want to report two possible bugs in the variable manager in Bricks 1.9.9:
If you change the name of an already created variable, Bricks wouldn’t change the name for all the instances already put in place. In my case I have a variable called “radius” and I’ve changed it to “radius5”. Anywhere var(–radius) has been used, it stays like this and breaks the design. Bricks doesn’t do search & replace, if you will. Is this the expected behavior?
Steps to reproduce issue:
Create a variable
Use the variable somewhere
Go to the variables manager and rename this variable
See how design breaks.
I have set variables for colors, so having “gray-900”, “gray-800”, “gray-200”, etc. In the RAW fields for colors, if I start typing gray, then I see all the gray variables, but if I type 200, 900, nothing pops up. Is this the expected behavior? Shouldn’t the match be loose?
Steps to reproduce issue:
Set a variable like “gray-900”.
Try to insert the variable in the RAW color typing the number, instead of the letters.
Doesn’t work on my side
Also, now that we have the variables manager, shouldn’t it be convenient to set a variable when typing its name right into the HEX section of the colors? This would save a few clicks here and there
Thanks very much!
[Please describe this bug in as much detail as possible so we can replicate & debug this bug]
Bulk actions: …such as renaming and duplicating. … However, it’s important to note that renaming a CSS variable does not automatically update its instances throughout your site.
However, in my opinion, it makes perfect sense for „numbers", as it can always happen that you don’t want to select a variable and instead want to enter the value, the variable picker would still always pop up - which could be annoying in the long run (the logic is identical for every input/RAW value field).
But there’s a simple “workaround”: search for --900. This should work (at least in 1.10beta).
I want to report two possible bugs in the variable manager in Bricks 1.9.9: