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

Property not being applied in FF, Chrome and Chrome Canary #16

Closed
tomliv opened this issue Sep 10, 2014 · 4 comments
Closed

Property not being applied in FF, Chrome and Chrome Canary #16

tomliv opened this issue Sep 10, 2014 · 4 comments

Comments

@tomliv
Copy link

tomliv commented Sep 10, 2014

I am using the normalize-opentype.scss file, importing it into my main sheet.

We are using TypeKit and the Scala Sans font.

In current versions of FF and Chrome (Mac) as well as current Chrome Canary (Mac), the font-feature-settings property are labelled as Unknown Property Name (in Chrome Canary) in Chrome Dev Tools and is just not listed at all in FireBug in FF (elements are listed - h1, h2 etc, but the rule is empty).

I cannot post a link at this time. If it is necessary, I can make a demo page.

@kennethormandy
Copy link
Owner

A demo page or CodePen or something would be great. My guess is that you need to change to the full character set, rather than the subset one:

typekit-set

Admittedly, I’m not entirely sure how this works with faces like Scala Sans which are outside the main library.

I find there’s five place where ligatures and other OpenType features can be intentionally or unintentionally omitted from use, I’m working on an article about it which can hopefully serve as better documentation for issues like this. If you don’t mind putting together a test case for me, that’d be super helpful to make sure I’m being thorough.

Thanks for filing an issue, I really appreciate it. ☕ ☕ (That’s 🍻 before 🕔)


Edit Re-reading this, it might also be related to #1. Are you using the Sass version without Autoprefixer?

@tomliv
Copy link
Author

tomliv commented Sep 10, 2014

Yes, that was it. Sorry. I must have missed that.

@tomliv tomliv closed this as completed Sep 10, 2014
@kennethormandy
Copy link
Owner

No need to apologise, glad it’s fixed. Just to clarify, was it the Typekit language support issue or the Autoprefixing issue?

@tomliv
Copy link
Author

tomliv commented Sep 11, 2014

It was the autoprefixing.

Thanks again.

@tomliv tomliv reopened this Sep 11, 2014
@tomliv tomliv closed this as completed Sep 11, 2014
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

2 participants