- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Apr 2020 10:18:15 +0000
- To: public-css-archive@w3.org
> Maybe any new generics should be handled via some other syntax, such as font-family: generic(<name>), to minimize the risk of disrupting legacy content. It would then be possible to extend the set of supported generic <name>s without conflicting with actual font names. I was thinking along similar lines. Another possibility may (??) be a prefix character that creates a name one is unlikely to see for naming fonts, eg. -fangsong, ~fangsong, :fangsong, _fangsong, etc. (those may not be good examples, but they show what i mean). -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4910#issuecomment-621111645 using your GitHub account
Received on Wednesday, 29 April 2020 10:18:17 UTC