- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Sat, 13 Jul 2019 23:32:49 +0000
- To: public-css-archive@w3.org
Thank you for the detailed response, @othermaciej. Yes, you summarized my concerns fairly. But I remain unconvinced. I still don't see an authoring use case for "match the system standard serif font" because most systems don't have standard serif (or rounded or monospace) fonts. @litherum's proposal states that there is an authoring demand to access _these particular_ new fonts on Apple devices. But that's different from the argument for `system-ui`, which was that many major websites were crafting font stacks designed to match the standard system font for each OS. I'd also be curious to see any evidence of web incompatibility for changing the Times/Arial defaults — just because something would change doesn't mean it would be incompatible. And if changing the generics is incompatible for a given website, then that website is probably already broken for many users. If there _is_ a web compability reason to map the generic font names to specific fonts, we should put that in the spec. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4107#issuecomment-511161026 using your GitHub account
Received on Saturday, 13 July 2019 23:32:51 UTC