- From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Oct 2019 18:59:21 +0000
- To: public-css-archive@w3.org
The observation that we made when we implemented optical sizing is that 1 typographic point = 1 CSS pixel. This is clearly true: Safari, Firefox, Chrome, Pages, Microsoft Word, raw Core Text, and TextEdit all agree. Here is an image of Ahem rendered in all of those using a size of 48 typographic points:  You can see that it's the same size in all of these different apps. In addition, Pages even puts units on the font size: "pt" and the documentation for raw Core Text (the second to rightmost app in the above image) also [indicates](https://developer.apple.com/documentation/coretext/1509153-ctfontcreatewithname?language=objc) that its size is in points: > The point size for the font So, when we apply an optical-sizing value of X typographic [points](https://docs.microsoft.com/en-us/typography/opentype/spec/dvaraxistag_opsz), that is equal to CSS pixels, and we apply this correctly. I'm not making a point about what the designers of desktop typographic systems intended to be true. Instead, I'm making a point about what is, de facto, true in reality. -- GitHub Notification of comment by litherum Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4430#issuecomment-543315394 using your GitHub account
Received on Thursday, 17 October 2019 18:59:23 UTC