- From: Jany Belluz via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Apr 2023 11:20:38 +0000
- To: public-css-archive@w3.org
Hello all, I'm expressing support for this proposal on behalf of Dalton Maag, in particular for the option `font-optical-sizing: 0.75;` and if possible to have that as the recommended default. As others have said, this would allow browsers to align with other publishing applications and the OT spec in their handling of the opsz axis. To give a concrete example of why we believe this matters, we recently released the typeface [Marble Arch](https://www.daltonmaag.com/library/marble-arch) and the designers who defined and tested the behaviour of the opsz axis found that the observed difference in web browsers and in print was so important that we considered the option of releasing two versions of the font, one specifically for use on the web and another for use in desktop applications. In the end we decided it would be too confusing and inconvenient for users to go down that route, and we only released a single version of the axis that uses the definition of the OT spec and that looks best in desktop publishing apps. However, this means that currently the font looks "more delicate" than intended in most browsers, and that conditional glyphs (such as the ear of the lowercase /g) trigger at a lower font size than what designers intended. Another argument for the sake of consistency between browsers and desktop applications is Figma and other web-design related apps, which work as desktop applications and then can export automatically some HTML and CSS. The inconsistency in treatment of the opsz axis means that the exported designs would render inaccurately in browsers. -- GitHub Notification of comment by belluzj Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4430#issuecomment-1525515117 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 April 2023 11:20:40 UTC