- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Apr 2018 15:59:48 +0000
- To: public-css-archive@w3.org
I realize the spec has always been this way, but it's always seemed less than optimal to me. Ideally, I think neither stretch nor weight should unconditionally take precedence over the other; rather, we'd have a function that defines the "distance" of a given face's (stretch,weight) tuple to the author's requested properties, and choose the "closest" face available in the family. How best to define such a distance function is of course far from clear, but perhaps it's worth trying? This could also be an opportunity to revisit the current behavior where a request for `font-stretch: 111%` in a family that has faces with stretch values of 100%, 110% and 200% will prefer the 200% face, even though it is far more stylistically extreme than what was requested. -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2537#issuecomment-382046927 using your GitHub account
Received on Tuesday, 17 April 2018 15:59:50 UTC