- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Oct 2016 20:47:35 +0000
- To: public-css-archive@w3.org
That seems to assume that each font covers the same range, though. If font A covers 0.6 to 1.3 and font B covers 0.5 to 0.8 then it would be weird to have both of those normalized to a 0 to 1 range which means different things for the two fonts. Its the same as with weights - if font A covers 500 to 700 and font B covers 600 to 999 I don't want to see both hidden under "the font covers 0 to 1" and have to discover what weights that is exactly. Lastly, designers will see these values exposed in things like Photoshop and InDesign. They should be able to use those same values in their CSS, not have to convert them to special CSS vales. I agree about clipping rather than ignoring out of range values. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/573#issuecomment-251794757 using your GitHub account
Received on Wednesday, 5 October 2016 20:47:44 UTC