CSS values different to property entered
Apologies if this is something that has already been asked - I did have a look but couldn't find anything similar.
I've noticed that the values shown in the Properties panel seem to be different to the ones in the CSS panel - if my font is set to 24px in the Properties panel for example, it is showing as 32px in the CSS panel. I've also noticed a similar issue for border radius on rectangles and widgets - the "Round" property within the Border section in the Properties panel is set to 22, but in the CSS panel it says "3px border radius". Width and height values do the same.
In all cases, the CSS panel seems more accurate, but I don't want to have to flip between the two to get an accurate font, border radius or size, so am I doing something wrong?
Dear Libbie,
Sorry for our late response. The properties panel shows the size of the font in pt (points) and the CSS panel shows in px (pixels). This is the reason of the difference between numbers. In the case of the border, the properties panel is showing the value in percentage (0-100) and the CSS shows the value of the circle radio in px. I hope this helps.
Best,
Dear Libbie,
Sorry for our late response. The properties panel shows the size of the font in pt (points) and the CSS panel shows in px (pixels). This is the reason of the difference between numbers. In the case of the border, the properties panel is showing the value in percentage (0-100) and the CSS shows the value of the circle radio in px. I hope this helps.
Best,
Hi Sonia, thank you for the response, I had managed to find some other questions that were not too dissimilar to mine and worked out it was using pts instead of pixels. I also asked if there was any update about changing this to pixels, but was told it wasn't happening - is there a reason for this?
I was thinking about using Justinmind as a design tool as well as for prototyping, but this really would limit its use to me personally. If you're designing for the web, you need to work in a unit that works on the web, especially if you're using an established design system that is set in pixels, which I am. It adds unnecessary steps to my (and probably others) workflows when you have to flip back and forth between the Property and CSS panels to check you're using the correct sizing. I don't personally know anyone aside from print designers that actually use points as a unit - was Justinmind originally meant for this? I would love to hear your thoughts on this, as so far it's just been a no, and I'm curious!
Hi Sonia, thank you for the response, I had managed to find some other questions that were not too dissimilar to mine and worked out it was using pts instead of pixels. I also asked if there was any update about changing this to pixels, but was told it wasn't happening - is there a reason for this?
I was thinking about using Justinmind as a design tool as well as for prototyping, but this really would limit its use to me personally. If you're designing for the web, you need to work in a unit that works on the web, especially if you're using an established design system that is set in pixels, which I am. It adds unnecessary steps to my (and probably others) workflows when you have to flip back and forth between the Property and CSS panels to check you're using the correct sizing. I don't personally know anyone aside from print designers that actually use points as a unit - was Justinmind originally meant for this? I would love to hear your thoughts on this, as so far it's just been a no, and I'm curious!
Replies have been locked on this page!