- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Tue, 03 Jul 2018 07:19:15 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `Prioritizing font-stretch over font-weight seems wrong`, and agreed to the following: * `RESOLVED: closed no-change except if the filer wrote a test and UA shows diverging behaviors` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: Prioritizing font-stretch over font-weight seems wrong<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/2537<br> <frremy> fantasai: if you have font-family which "normal + wide" and has a bold for "normal" but not "wide"<br> <frremy> fantasai: if the author specifies "wide bold" what do you get?<br> <frremy> fantasai: I think you want "bold"<br> <frremy> fantasai: right now, we specify "wide"<br> <frremy> fantasai: I think "bold" is more semantic<br> <frremy> chris_: we have no test for that<br> <frremy> chris_: and I don't know if we can change implementations<br> <frremy> myles: every time I try to change how this selection happens, I get tons of bugs<br> <frremy> myles: so it might be a good idea, but I don't think this is very doable<br> <frremy> florian: you can synthetize bold but not font-stretch<br> <frremy> florian: so it's better to pick "wide" and fake "bold"<br> <frremy> florian: in the reverse case, we can't fake "wide" so the layout ends up very different<br> <frremy> RESOLVED: closed no-change except if the filer wrote a test and UA shows diverging behaviors<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2537#issuecomment-402037877 using your GitHub account
Received on Tuesday, 3 July 2018 07:19:21 UTC