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: Laurence Penney via GitHub <sysbot+gh@w3.org>
Date: Wed, 07 Jul 2021 16:41:22 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-875758012-1625676080-sysbot+gh@w3.org>
> @Lorp in your [May 12 proposal](https://github.com/w3c/csswg-drafts/issues/4430#issuecomment-840207323) am I correctly understanding that you are proposing **no changes to all current browser implementations**?

No, I’m proposing **no changes to default behaviour in currrent Apple browser implementations**.

> 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.)

I’m no expert on cross-platform philosophy, but it seems a pity if content creators have to bear in mind a sporadic 4/3 factor if they care about precise glyph shapes, even when they specify font size and know the size of device they’re dealing with.

> Second, I now advocate updating the OpenType spec to document what is actually implemented. @Lorp put it concisely:
> 
> > * opsz = font-size in px for screen media
> > * opsz = font-size in pt for print media

I’m not sure about it going into the spec like that, even if it is universal behaviour in browsers. It’s very much a CSS thing, and OpenType is not beholden to CSS, is it? It makes sense for such a compromised implementation to remain browsers’ default only if it’s easy to customize. And BTW there’s no real reason it needs to remain the default forever.

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 July 2021 16:46:28 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:27:25 UTC