- From: Peter Constable via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Jul 2017 16:33:47 +0000
- To: public-css-archive@w3.org
Note that the axis ranges of AAT variable fonts are undefined and hence interoperable. That was the reason for this significant change when adding variations in OT. For example, suppose I want to use Skia in a font-family chain, but also want to specify a particular weight: font-family: "Avenir Next Variable", Skia; font-weight: 550; What am I going to get if Skia gets used? Maybe Safari has a deterministic answer, but no other browser has a way of knowing what that would be, and may have a different answer. Hence, it's completely unpredictable from a user POV. Axis ranges in AAT variable fonts have no interoperability story. They can only be treated like custom (non-registered) axes, in spite of the fact that AAT recognizes some of the registered axis. The only way I can see to make AAT variable fonts work with CSS would be to specify in the spec that, given a non-OT variable font (recognizable by presence of 'fvar' but without a 'STAT' table), all axes must be treated like custom axes, meaning that the can be set using font-variation-settings but cannot be associated with the font-weight, font-stretch and font-style properties, and so cannot be referenced in font selection. -- GitHub Notification of comment by PeterConstable Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1531#issuecomment-315132279 using your GitHub account
Received on Thursday, 13 July 2017 16:33:53 UTC