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

@tiroj writes:
> if an override mechanism has been used to explicitly specify a 24pt opsz instance … that explicit setting should be preserved even when text scaling involves re-layout. That is, explicit opsz selection should be understood as text styling, akin to setting an explicit weight, witdth or slant, as distinct from opsz selection as text automation

If you accept this is a legitimate desire for CSS authors, then I point you to my [comment last week](https://github.com/w3c/csswg-drafts/issues/4430#issuecomment-693581342) which adds to my list of examples, so I now repeat all seven for clarity:

```
font-optical-sizing: auto;     /* get font-size in pt or px, use as opsz */
font-optical-sizing: 2;        /* get font-size in pt or px, *2, use as opsz */
font-optical-sizing: px;       /* get font-size in px, use as opsz */
font-optical-sizing: pt;       /* get font-size in pt, use as opsz */
font-optical-sizing: 2 px;     /* get font-size in px, *2, use as opsz */
font-optical-sizing: 2 pt;     /* get font-size in pt, *2, use as opsz */
font-optical-sizing: 10 opsz;  /* ignore font-size, use 10 as opsz inheritably */
```

@svgeesus:

> authors may choose to prefer a heavier/lower-contrast or lighter/higher-contrast rendering for a specific face, than the font designer provides by default. In the same way that they may prefer the look of a weight of 650 for bold or 424 for book, compared to what the font designer picked as a default

Indeed, though the logical conclusion of your remarks goes further and allows direct glyph shape selection via `opsz` value.

I’d be amazed if specific glyph shape selection is not seen as legitimate for CSS authors. I cannot support an `opsz` implementation in CSS that offers a “miraculous” automatic setting without a manual setting.


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 23 September 2020 20:32:10 UTC