- From: David Berlow via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 May 2020 12:09:30 +0000
- To: public-css-archive@w3.org
While I agree 1/2-way with: As @twardoch said: "When in doubt, it's better to user the lower opsz value. Choosing a “too low” opsz value will get you slightly clunkier text but it will be readable. Choosing a “too high” opsz value will get you unreadable text that’ll defeat the purpose of font-optical-sizing." The importance of size can cast doubt on that doubt, if it does not entirely reverse it. So, when in doubt at *small* sizes, it's better to use the *smaller* opsz value, as more readable text is likely while choosing a “too high” opsz value is likely more economical, and likely less readable text. And, when in doubt at *large* sizes, it's better to user the *larger* opsz value, as more economical text is likely while choosing a “too low” opsz value is likely to have less economical text. (Verdana headlines anyone?) In some other words, it is not my belief that some vague sense of aesthetic improvement was, or should be today, the motive for the variation to larger optical sizes. It's got economic purpose in print and online. What I think this means to the implementation of opsz in css is that it should not end up cheating "down" everywhere, if possible. On Wed, May 20, 2020 at 5:48 AM Laurence Penney <notifications@github.com> wrote: > Thanks for this, @arrowtype <https://github.com/arrowtype>. It’s a good > suggestion. Even though CSS uses px as its basic measure, the notion of > optical size is usually talked about in “points”, and all user agents know > about CSS pt. As you say, it’s much more intuitive to authors if the > default is 1. They will, it may be hoped, get a sense of what it means to > make the value larger than 1 or less than 1. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/csswg-drafts/issues/4430#issuecomment-631368853>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAO5VDQ7N55CTEGTPVZ6HEDRSORP7ANCNFSM4JBXYCMQ> > . > -- GitHub Notification of comment by dberlow Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4430#issuecomment-631433695 using your GitHub account
Received on Wednesday, 20 May 2020 12:09:32 UTC