- From: litherum via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Sep 2016 17:57:40 +0000
- To: public-css-archive@w3.org
I think all the browsers agree on how this is handled. I tested this by making an Ahem font, but didn't including the letter "m". Then, I made a second Ahem font, but this one has a taller ascent/descent, but doesn't include the letter "n". Both fonts include the letter "a". Then, I made a similar test as @fantasai except with this markup: ```html <p style="font-family: 'MyAhem', 'MyAhemLargeAscent'"><span>amn</span></p> <p style="font-family: 'MyAhemLargeAscent', 'MyAhem'"><span>mn</span></p> ``` As you can see in the results below, everyone seems to do the same thing. Here are the results (The first two lines are just making sure that the correct fonts are used; the relevant lines are the bottom two lines) ![macos](https://cloud.githubusercontent.com/assets/918903/18523527/77a5d442-7a69-11e6-9df9-6fbe36a60966.png) ![macos 2](https://cloud.githubusercontent.com/assets/918903/18523529/77c253ba-7a69-11e6-9bde-bcb95ea0f1ea.png) ![windows 10 2](https://cloud.githubusercontent.com/assets/918903/18523528/77be0788-7a69-11e6-8540-d4b75b890c70.png) ![windows 10](https://cloud.githubusercontent.com/assets/918903/18523530/77c2e820-7a69-11e6-9e6c-63a1c498f2bc.png) And here are the original files: [Fallback bounds test.zip](https://github.com/w3c/csswg-drafts/files/472995/Fallback.bounds.test.zip) -- GitHub Notification of comment by litherum Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/391#issuecomment-247100829 using your GitHub account
Received on Wednesday, 14 September 2016 17:57:47 UTC