Skip to content
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

Fira Sans CDN Font does not support "tnum" feature #1582

Open
mofojed opened this issue May 30, 2018 · 3 comments
Open

Fira Sans CDN Font does not support "tnum" feature #1582

mofojed opened this issue May 30, 2018 · 3 comments

Comments

@mofojed
Copy link

mofojed commented May 30, 2018

When Fira Sans font is included in a page using the CDN link, the font-feature-settings: "tnum" CSS property doesn't work.

Oddly enough, if I download the Fira Sans font from Google's site and install it locally, the feature setting works: https://fonts.google.com/specimen/Fira+Sans?selection.family=Fira+Sans
It also works if I link the font from Mozilla's CDN.

It's only when I link to Google's CDN and don't have the font installed locally. I've made a plnkr to demonstrate the issue: https://plnkr.co/edit/SnSm7siVrk5AiQq9NDUK?p=preview

@davelab6
Copy link
Member

davelab6 commented Jun 3, 2018

We subset out OpenType features to improve latency. For now, self hosting or using another font CDN is the only way to use discretionary OpenType features.

@laerm0 laerm0 added this to the Questions about Google Fonts service (API) milestone Jan 28, 2019
@laerm0
Copy link
Contributor

laerm0 commented Jan 28, 2019

Should we close, @davelab6 ?

@lundmikkel
Copy link

Why not allow us to include them with some kind of options? Say https://fonts.googleapis.com/css?family=Montserrat:300,400,500&display=swap&settings=tnum.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants