- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Feb 2021 16:24:22 +0000
- To: public-css-archive@w3.org
Looking over the proposals here, I believe I'm still the most in favor of adding descriptors to `@font-face` that "adjust" the used values of the various font-related properties when that font is the primary font for a text run. Aka what @jfkthame suggested in <https://github.com/w3c/csswg-drafts/issues/126#issuecomment-764641927>, just folded into `@font-face` itself rather than indirecting thru a new rule. (In particular, I like their "interpolate for in-between values" part.) The most relevant factor for me in choosing this vs Myles's suggestion of putting these per-font adjustment into the property syntax (<https://github.com/w3c/csswg-drafts/issues/126#issuecomment-764183953>) is whether these adjustments are likely to be common to every use of the font on a page (and thus best to fold into a single at-rule) or specialized/distinct for particular uses (and thus best to target to the exact usage). If they're likely to be common, then using per-property means a *lot* of repetition, and it's easy for these declarations to grow out of sync with each other over the lifetime of a page. If they're likely to be specialized, then using at-rule means you'd need to create several distinct @font-face rules, one for each specific instance, which feels pretty clumsy. I *think* it's more likely for the adjustments to be common to the page, but that's just based on my intuition. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/126#issuecomment-773433362 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 February 2021 16:24:23 UTC