W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2021

Re: [csswg-drafts] [css-fonts] Proposal to extend CSS font-optical-sizing (#4430)

From: Alex via GitHub <sysbot+gh@w3.org>
Date: Fri, 16 Jul 2021 05:14:56 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-881183196-1626412494-sysbot+gh@w3.org>
> Assuming so, I think there's 2 things to do.
> 
> First, I think @litherum 's [issue 1102532 on the Chromium bug tracker](https://bugs.chromium.org/p/chromium/issues/detail?id=1102532), proposing Chromium use CSS pt on Windows instead of px, be closed as "WAI". (While @litherum chose to make Webkit/Safari on macOS apply `opsz` consistently with native macOS apps rendered directly with Cocoa/CoreText, it makes sense to me that cross platform browsers like Chromium will choose cross platform consistency over matching local platforms.)
> 

As a user I definitely prefer "same system" consistency to cross platform consistency. As I don't use Safari or own a Mac, being consistent with that for me really means "Inconsistent with every other app on my device". Why not be inconsistent with macOS then to follow other platforms?

I also wonder how this is going to interact with things like Electron and Windows 11 using a variable UI font, are we going to end up with every electron app using the wrong instance of the UI font on Windows because it's trying to follow the type sizing notions of macOS? If Android eventually gains one the problem would just spread there as well.

-- 
GitHub Notification of comment by TheDecryptor
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4430#issuecomment-881183196 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 July 2021 05:14:57 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:39 UTC