See this Loom.
I can’t add variations for Italic once the Normal weights exist.
Actually, it is an even bigger problem.
If I use a Variable font and add a bunch of weights, save and refresh, all the variations disappear.
Hi Alan,
Thanks so much for your report!
This is not necessary, as usually, you only need a single font file for variable fonts (depending on the font). Example Roboto: roboto supports the weight axis from 100-900, i.e. all font weights between 100 and 900 are already included.
If you download from google, you’ll get two font files:
The first one is the italic font file which supports the width and the weight axis. The second one is the regular font file, which supports the width and the weight axis. So if you want to use italic, set it tup like this:
Now you can decide wether you want to use the font-weight dropdown, or the font-variation settings to set the font-weight:
So overall, it’s not a bug, but a misunderstanding of how variable fonts work, right?
Best regards,
timmse
Oh cool. I’m used to the old custom fonts when you have to add each weight, or they did not display in the selector. This is even better.
However, this true for Variable fonts. I have not tried nonvariable fonts. Would this be a bug affecting them ? Worth checking .
I get that.
With Bricks 1.x.x using a variable font, you had to define each weight using the same file or the weights did not show up in the select.
That is why I did the same in the new font manager. I now know that it works differently.
The issue I experienced was that if you set weights for the Normal font, the UI fails when you try to do the same for the Italic font.
I don’t know if that will be an issue when you don’t use a Non-variable font?? Does the logic that detects that you have already defined the weight/style combination take the actual file into account?? I don’t know. I’ll give it a try tomorrow and report back if it has the same issue.
Same issue here.
- Using a variable font file only shows the font weight selected from the Font Manager, even though the front end CSS specifies a different font weight. It’s as if Bricks is treating the variable file as a regular font file. See second photo showing thin fonts even though CSS says “400” normal font.
- It is not possible to provide multiple variations of the same variable font file. This might be by design, but in that case issue #1 needs to be fixed.
If you are only supposed to provide a variable font file once, why is there still a way to select the weight and font style for that file (see photo)?
Follow up video. This shows that the issue has nothing to do with Variable fonts. The bug exists even if I’m selecting different font files.
Hey @alanblair ,
Thanks so much for the video!
Yes, I can reproduce this problem. The font preview seems to be a bit confused 
-
Can you provide me with a link to the installation from your screenshot (assuming it’s still set up as in your screenshot)?Edit: I see what you mean. Could you please create a separate report for this (and tag me), as I’ll create a separate task for it, since it’s different from the issue reported by Alan. -
True, that’s not yet possible. However, we already have an internal task for this.