- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Aug 2019 16:57:17 +0000
- To: public-css-archive@w3.org
I see two ways people might want to use these: * People find these specific fonts pretty and want to use them. If so, the use case is **not** solved by having keywords that don't promise to match these specific fonts, and merely happen to do so on the first system on which they ship, may stop matching these specific fonts in the future, and will match different fonts on different systems. * People want to match the look and feel of native apps. In that case, they not only need a keyword to match the fonts that are used in native apps, but also to match the platform conventions about where these fonts are used. And these conventions are OS specific, the resulting layout will be odd on different OSes than the one the author had in mind when designing the page/app. Given that these fonts are fairly generic, and that the current design trends are fairly flat / minimalist, then it may not be too jarring now. But if you comparing very different OS styles, the problem becomes more apparent: if an app is used with these fonts to look native on iOS, it probably would look alright on android, but it absolutely would not look native on windows 95, regardless of how you mapped the fonts. So, all in all, it doesn't seem to me that the proposal solves the use cases, as I understand them. I think the way @fantasai is proposing to handle them in https://github.com/w3c/csswg-drafts/issues/4107#issuecomment-525824422 is the way to go if we do it, but I am not convinced we should. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4107#issuecomment-525832007 using your GitHub account
Received on Wednesday, 28 August 2019 16:57:18 UTC