- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Sep 2019 08:08:58 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `system-ui fonts`, and agreed to the following: * ``RESOLVED: Add them with the `ui-` prefix and make them not match if they're not available`` <details><summary>The full IRC log of that discussion</summary> <emilio> Topic: system-ui fonts<br> <emilio> GitHub: https://github.com/w3c/csswg-drafts/issues/4107<br> <fantasai> This is my position: https://github.com/w3c/csswg-drafts/issues/4107#issuecomment-525824422<br> <emilio> myles: should we expose these like any other font like "Times new roman" or as a keyword like a generic font family, which other browsers would also implement and whose behavior would change across OSes<br> <emilio> ... ?<br> <emilio> myles: I'd prefer the later<br> <fremy> @myles: does adding this as a keyword add a fingerprinting method? is it worth it? ;-)<br> <emilio> fantasai: (explains her position above)<br> <emilio> fantasai: tldr it makes sense to have system-ui keywords, but they should be exposed also behind an actual name<br> <emilio> myles: It's impossible for us to determine because the fonts are nice or because they're systemy<br> <emilio> Rossen_: how are you going to determine it?<br> <emilio> ... expose it with a proprietary name and you're done<br> <emilio> koji: I think regardless of exposing them via the name I think there's use case for the keywords<br> <emilio> florian: I think they should be exposed by name, and if after that there's still users asking for that then we're done<br> <Rossen_> q?<br> <emilio> ... but just font families is not the only thing that emulating the system<br> <emilio> s/that/for<br> <emilio> myles: but it's a required part of matching the system, regardless of the rest of the design<br> <emilio> florian: it doesn't seem helpful to use system-ui vs. named, if you can just ua-sniff and set the font name<br> <emilio> dino: it may help authors in other systems too<br> <emilio> koji: we learned from system-ui that authors don't want the exact same font as the system<br> <emilio> ... on windows server a bunch of big pages didn't want the system font which was tahoma, they wanted segoe instead<br> <emilio> Rossen_: that's why when we released segoe we did it as a font not as a ui keyword<br> <emilio> florian: that's interesting, so this is appropriate in the sense that people wants ui fonts, but not the system ui font<br> <emilio> myles: so ui-serif rather than system-ui-serif?<br> <emilio> florian: if that's the use case that sounds fine<br> <emilio> nmccully: having a shorthand seems useful to guarantee that the font is current, is there, and not have to worry about the list of system fonts<br> <leaverou> q+<br> <emilio> myles: so it seems we're coalescing to add `ui-rounded`, `ui-serif`, `ui-monospace`, ...<br> <emilio> florian: I'd also also encourage apple to expose them by name<br> <emilio> nmccully: that seems useful<br> <emilio> myles: ok, we'll do both<br> <emilio> florian: less sure about *-rounded<br> <emilio> fantasai: what do we do for `ui-rounded` if there's no rounded font?<br> <emilio> ... maybe you have only arial and times?<br> <emilio> ... what do you fallback to?<br> <emilio> florian: I'd propose just for it not to match so it falls back to the next of the list<br> <emilio> leaverou: if we need more granularity to system ui fonts why mapping them to apple?<br> <emilio> ... why not system-ui-titletext?<br> <emilio> myles: when a platform has a different font for titletext we can consider that<br> <emilio> RESOLVED: Add them with the `ui-` prefix and make them not match if they're not available<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4107#issuecomment-532111422 using your GitHub account
Received on Tuesday, 17 September 2019 08:09:00 UTC