-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "variable fonts" option #164
Comments
Hi @Rvervuurt
|
I will add an example to the documentation |
Ah yes, much better! This doesn't trigger an error. |
Hi, this works as expected while in development but once the nuxt app is built the font doesn't work... is it just me or is someone else experiencing this issue? Once built it outputs this inside the @font-face {
font-display: swap;
font-family: Manrope;
font-style: normal;
font-weight: 200 800;
src: url(/_nuxt/Manrope-200 800-2.26287892.woff2) format('woff2');
unicode-range: u+0301, u+0400-045f, u+0490-0491, u+04b0-04b1, u+2116;
} That In the You can see a reproduction here: https://debugfontissue.davidegaio.com/ (user:
Note: I'm replying here because I think it's related to this issue but if you prefer I can create a new issue for this, let me know |
Does it accept other parameters, such as opsz, FILL, GRAD? The options I tried: googleFonts: {
families: {
'Crimson Pro': {
wght: '200..900',
FILL: '0..1'
}
}
} The code above generated the URL: https://fonts.googleapis.com/css2?family=Crimson+Pro:FILL,wght@0,200..900;1,0..1&family=Material+Icons&display=swap The return explains that: Axes must be listed alphabetically (e.g. a,b,c,A,B,C). |
I would like to add fonts as variable fonts, but this doesn't seem supported.
Now, adding fonts looks like this:
But this just adds 200, 400, 600 and 700 font weights and doesn't allow for animation of the font weight.
According to Google's own documentation, variable fonts are added as a range (
200..700
) instead of steps (200,400,600,700
), so the above could could look like this:Is this something you could consider adding?
The text was updated successfully, but these errors were encountered: