- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Sun, 21 Jul 2024 16:03:35 +0000
- To: public-css-archive@w3.org
LeaVerou has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-fonts] Specify `generic()` versions of existing generic font families == Re: https://drafts.csswg.org/css-fonts/#generic-family-name-syntax It appears we introduced a `generic()` syntax for new generic font families, but existing generic font families are still only specifiable using keywords. Specifying them using `generic()` as well is not only more consistent and more readable, but it would also facilitate feature detection via `@supports` — which is currently impossible ([this post](https://blog.jim-nielsen.com/2022/font-family-and-supports/) recommends a JS method, but it doesn’t actually work). Precedent: when we switched to a double colon for future pseudo-elements, we supported both syntaxes for existing pseudo-elements so that authors could eventually move towards that as a convention for all pseudo-elements. It’s the same here: we want authors to eventually move towards `generic()` for all generic font families. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10608 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 21 July 2024 16:03:36 UTC