search

kennethormandy / normalize-opentype.css

Adds OpenType features—ligatures, kerning, and more—to Normalize.css.
http://kennethormandy.com/journal/normalize-opentype-css
MIT License
791 stars 29 forks source link

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

Closed tomliv closed 10 years ago

tomliv commented 10 years ago

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 commented 10 years ago

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. :coffee: :coffee: (That’s :beers: before :clock5:)

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

tomliv commented 10 years ago

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

kennethormandy commented 10 years ago

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

tomliv commented 10 years ago

It was the autoprefixing.

Thanks again.