- From: Neil Jenkins via GitHub <sysbot+gh@w3.org>
- Date: Mon, 11 Sep 2017 03:57:05 +0000
- To: public-css-archive@w3.org
Yes, setting up `@font-face` rules to map to different weights is fine for the custom font case. The trouble is if you need to use built-in fonts, and you want to map a different weight for the Windows vs Mac system fonts, to take a real-world example. I know backwards-compatibility constraints may prevail, but I suspect most developers that haven't read the spec would intuitively expect the "nearest" weight to apply rather than the more complex partitioning algorithm that we currently have. It seems simpler and more useful to me. -- GitHub Notification of comment by neilj Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1701#issuecomment-328409206 using your GitHub account
Received on Monday, 11 September 2017 03:57:00 UTC