I totally agree, also the is not a feature that was requested
I also find it super weird working without units.
I love it the way it is now. Of course the default is pixels. Type in your custom unit by hand. Team: please do not reintroduce the unitsâthey are so destructive to the editor design wise and they used to slow us downâŚ
1 Like
omg⌠another one - and on every other channel people are complaining, even in here. but yeah ⌠âi love it, and i dont care if anyone other doesnt understand how to useâ âŚ
hopefully we will see an option for both versions.
2 Likes
btw another thing to add. if it will be kept that way its a 100% confirmation for me bricks is obviously not planing to grow more.
Actually, I guess we should shut up and let the team do their work and not distract and confuse them with our pathetic quarrel over units. Yeah. If I just could close this topic:)
2 Likes
Okay people, as the saying goes âif the mountain doesnât go to maomaâŚâ I have chosen to try, try and try and I have already gotten used to the new way of working and the truth is that it is a bit difficult at first, but once Once you understand how it works it can be a bit faster to work with.
1 Like
I also donât see the reason for removing unit dropdown. I know that from developers perspective it is harder to maintain it and there are more room for errors, but to be honest, it was working pretty well already.
Now, somebody said that if you use variables itâs better if we donât have unit dropdown and that is true, but if we use values, itâs was better before. Why?
- We could select the value with mouse
- Users, which are new to web development donât know all the units they can use and there was a FB post from that kind of user where he said that he didnât remember what unit should be for full screen. Is it âfwâ, is it âvhâ or what. And before, he just opened the dropdown and he saw the unit.
- Before, if we wanted to select only value, we could do it with doubleclick and that was it, now if we want to select it, (or if we want to select a unit only) and we want to select it with mouse, itâs harder and it also changes the value if we move mouse a little up or down.
So, I agree that it should be optional. Or if it was removed because of variables, they should hide the dropdown if they detect we type variables inside.
Overall, I donât like this change. If it will be kept this way, I hope someday some kind of dropdown will get implemented back.
3 Likes
Guys I would like to say that I am a beginner on bricks and I feel this conversation has left me out completelyâŚ
I hope to learn bricks better and at this stage I am not thinking about saving .00001 of a second on the keyboard. A dropdown of some kind would be a great visual que especially as a number on its own means nothing to me!!!
I just ask the team to have some consideration for new usersâŚ
3 Likes
I think the problem here is logic, consistency and accessibility.
On one side you have margin and padding âdumbifiedâ (sorry for the term, I donât think itâs dumb, but this passes the message) because people donât like the default order that was more logical and how CSS order them. For a tool focused on âdevelopersâ, this wasnât really a logical decision, although I do like the accessibility side of it. And I think it improves greatly on the UI, although compromising in using strings like vars. But fair enough.
On the other side it seems like removing the units was a decision made solely based on the âdeveloper mentalityâ, or in other words âif you are a professional you should knowâ. But this completely breaks accessibility (accessibility is more than supporting impaired people), negates the consistency and precedent around the âmore visualâ logic, and adds yet one more thing we should be remembering when setting-up units.
If the idea is to free up space, fine, remove the list. Thatâs no problem, but an indicator of what unit is being used inside, even if itâs the default unit is highly necessary! We need to be able to quickly see whatâs going on at a glance without having to stop everything to remember what was defined as a default unit.
So please consider a middle ground. This is essential for an efficient workflow.
.thanks =)
8 Likes
Just adding my voice to the choir that I find visible units useful.
- Thereâs plenty of space for a dropdown
- During the design process, itâs useful to be able to change values in 1-2 clicks.
Currently, if I want to briefly change rem to px to evaluate, and change back:
-
Click into value box
-
Navigate to the end of the value box if I didnât click it perfectly at the end
-
Press backspace 3 times
-
Type px
-
Press backspace twice
-
Type rem
Thatâs 11-12 actions simply to evaluate which value Iâd like to use.
Previous workflow:
-
Click unit dropdown
-
select unit
-
Click unit dropdown
-
select unit
Just 4 actions.
Iâd love the following workflow/features:
- A default unit would still take precedence (and could show up in the placeholder)
- The most recent unit section should override whatever is currently selected (ie; I choose rem via dropdown, but then type % on my next visit. % wins until the next selection)
- The dropdown would be keyboard navigable. This way, I could click into the dropdown, and toggle units with up and down arrows while keeping 100% attention on the design.
Please make my Christmas wish come true 
4 Likes
The previous action was only 2 (for me).
That was:
- Type the value+unit at the same time,
- Hit enter.
When the time I hit enter, the unit in the value field will jump to the unit selector. That means the unit selector would automatically detect what we typed in the value field.
After that, when I want to highlight the entire value (to change the value), I can just double-click and highlight all the values, but not the unit, because the unit is separated.
Now we want to carefully highlight the value, because the unit is there together.
1 Like
In my opinion this was a regression. We went from having multiple options to achieve the same goal, to having only one option that limits and breaks our workflow.
Im not one of using on-widget styles very often. I either use utility classes or my own custom-props as values. So having the extra space helps a lot.
But when I have to change something or to check what is there, this really makes my work harder. I also had some issues already where I typed ârmâ instead of âremâ without noticing, and couldnât understand why it wasnât working.
Granted I do this all the time with CSS, and have to review my dumb code decisions more often than I should (although VSCode helps a lot in that regard), the idea behind using a visual tool like Bricks is not to have to double check everything and work harder. Itâs meant to facilitate our lives. And so far Bricks has been amazing in that regard.
But some of the decisions lately have been very strange and illogical compared to everything else. Maybe there has been a change in direction, or maybe itâs just miscommunication (I know the team is working hard and I value and appreciate their work, and I donât think they should ask us about every single tiny decision made), but either way some of these decisions donât make much sense to me. Am I missing something?
2 Likes
But removing the unit is not a tiny decision, to be honest.
It creates such a serious inconvenience for us.
2 Likes
Sure, thatâs exactly what I meant.
2 Likes
I have the same issue with values changing when âmousing inâ or trying to select the number. Itâs super annoying and definitely broken.
1 Like
yes same here. reported already. and they said they will fix it. and I really hope this is fixed soon. crazy annoying