One reason (I guess) for `font-size-adjust` taking a number rather than an `auto` value is that this means it will behave consistently regardless of whether the author's first-choice font (from which the number would normally be derived) is actually present or not. With `auto`, the aspect would be computed from whatever fallback happens to get used; it would then provide consistency across additional fallbacks, but might be quite different from what the author expected based on the primary font they had named. An `auto` value would also mean, presumably, that if the primary `font-family` is a webfont, and hasn't yet finished loading, we can expect the size of any fallbacks that are being used (e.g. for content in other scripts) to change when the font-load does complete. (I'm not necessarily *against* an `auto` value, just trying to think through its implications. The behavior it enables would be significantly different from what an explicit `<number>` provides.) -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5539#issuecomment-700836153 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Tuesday, 29 September 2020 16:39:37 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:17 UTC