You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
This issue's about variable font on web, my experience using variable fonts in web development especially in front-end area really makes the job easier, because I only need to load one or maybe two files for several styles includes italic to avoid waterfall data fetching. Slanted "slnt" axis doesn't work on default html text formatting tags such a <i /> and <em /> even though by default these tags have font-style: italic; on any browser.
Describe the solution you'd like
As a GF Guide recommendation to separate roman and slanted (to be italic)
Describe what you've tried so far
I never touch the masters font file, but for temporary solution for web development is manually adding:
Hey, thanks for asking! Yeah, I should split the variable font for web, and add that to the release. It is annoying browser support is so bad, but it is what it is.
For now, you can split it on your own in two ways:
Is your feature request related to a problem? Please describe.
This issue's about variable font on web, my experience using variable fonts in web development especially in front-end area really makes the job easier, because I only need to load one or maybe two files for several styles includes italic to avoid waterfall data fetching. Slanted
"slnt"
axis doesn't work on default html text formatting tags such a<i />
and<em />
even though by default these tags havefont-style: italic;
on any browser.Describe the solution you'd like
As a GF Guide recommendation to separate roman and slanted (to be italic)
Describe what you've tried so far
I never touch the masters font file, but for temporary solution for web development is manually adding:
or in the modern environment like TailwindCSS
However it breaks the native html text formatting tags and TailwindCSS experience for entire web pages
The text was updated successfully, but these errors were encountered: