- From: Dave Crossland via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 May 2020 04:14:41 +0000
- To: public-css-archive@w3.org
>> > The issue here isn't just of consistency in implementation — of getting the same opsz instance for the same _nominal_ type size in different platforms —, but getting the opsz instance that the type designer has created for an _actual_ size. Otherwise there's no point in calling this optical. Oh wow, I am amazed to see @robmck-ms actually NAILED this back in December 2016 in #807: > One could also look at using physical, rendered size on screen, but that too has many problems. ... In the end, the approach we found worked best was that optical style was a function of the text size _within the document_. E.g. If the user selected 10pt type in Word or in CSS, then that is used to select the optical size, regardless of how big the letters end up in the real world. I.e. Pinch-zoom and other zoom actions (accessibility, ctrl-+, etc) happen _after_ style selection. > ... > So, for HTML/CSS, I'd propose the value of the font-size parameter, converted to points, would be used for optical style selection. And I see @litherum agreeing at that time with this, and me and @dberlow warning about this 4/3 issue. And here we are. -- GitHub Notification of comment by davelab6 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4430#issuecomment-632469142 using your GitHub account
Received on Friday, 22 May 2020 04:14:42 UTC