- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Dec 2019 00:52:38 +0000
- To: public-css-archive@w3.org
> I think you also need to clarify that these new values are keywords, like `<generic-family>`, If the changes suggested in #4442 are accepted, we can just include these keywords in `<generic-family>` and not worry about repeating the syntax details. For the note: For authors, we want to emphasize that using these keywords will get different results on each platform (though hopefully consistent within an OS), and the mappings may change over time. If they want specific fonts, they need to use specific font-family names. I think Myles' note covers that. For user agents, the "encouragement" is to give authors that choice, by making fonts available either by keyword or by name. It might be helpful to therefore break this into two separate notes: > Note: These standard font families are expected to exist on different platforms, but be backed by different fonts. The mappings may also change over time, as the operating system fonts change. Authors who wish to use specific fonts should specify them by font-family name, rather than with these keywords. The keywords are specifically intended for authors who wish their design to always match the current operating system typography. > > Note: To avoid authors using these keywords when they really want a specific font-family, user agents are encouraged to also expose the system font families by other, platform-specific, font-family names, in addition to the keywords given here. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4107#issuecomment-561425029 using your GitHub account
Received on Wednesday, 4 December 2019 00:52:40 UTC