Hey Bricks team. In 1.8 beta update changelog, specifically in regards to the Google Font API v2, it is noted that:
The “font-variation-settings” setting is only visible when a “font-family” has been selected. As we need to know the font-family in order to add the font axis key & value to the Google font URL.
So I did some tests and found that I would have to respecify the font-family for each time an element/class has a different font-variation-settings. IMO, the field should be kept visible at all time simply because it feels like an unneeded step to respecify the font-family since they already inherited the font-family from the body anyway.
Also, for some of us who do not use Google Fonts and/or have it disabled but instead uses custom variable fonts, none of those API issues will affect us anyway.
Prior to updating to 1.8 beta, I uploaded a variable Google font (Gantara) and set the weight to 750 using the font-variation-settings control. On updating to 1.8, that control has disappeared but the 750 weight is still working. I now wish to vary the weight slightly, but cannot see the setting as it’s hidden.
The font-variation-settings control needs to be visible at all times.
Patric, I’m not referring not the font setting in the Custom Font upload but in the Typography Style setting:
Prior to the 1.8 beta, the font-variation-settings is always visible. In 1.8 beta, a font-family has to be specified, only then the field will be visible.
Yes. And actually we should just use regular font-weight to set the weight. Not necessary to use font-variation-setting: ‘wght’, which creates two different system in the builder for regular font and variable font. But the condition is to properly declare the variable font. I created a post for it. Issue of setting variable font
