- From: Carlos Lopez via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 May 2019 18:05:21 +0000
- To: public-css-archive@w3.org
@AmeliaBR >System fonts that include font size are part of the spec for the font shorthand property. The -apple-system-* font keywords are unique because they map to a font family without specifying a font size or bold/italic etc. Unless I'm misunderstanding your comment, `-apple-system-body` does change the `font-size`. That's really the way Dynamic Type works. You set it in iOS settings and then any Safari page that uses that `font` property will get all the font styles. I explained this a bit better in a previous. https://github.com/w3c/csswg-drafts/issues/3708#issuecomment-477433666 This [Webkit blog entry](https://webkit.org/blog/3709/using-the-system-font-in-web-content/ ) states: >These text styles identify more than simply a particular font family; instead, they represent an entire style, including size and weight. @cookiecrook Also made a great point that an OS can have system-wide bold/italic setting: >iOS has a system-wide setting to enable bold text*, which is reflected in the system weight. That's why I'm advocating for `font: system` which would have more benefits. That's also why I was unsure if I should open up another issue that is specifically targeting the entire system font, versus just the font-size. >Which is a limitation of the browser UI, not a limitation of the spec. The problem is, there's no spec for how and when to use the default system font size, so any implementation of it would be custom. I came across this issue because I directed here by the Chromium team. https://bugs.chromium.org/p/chromium/issues/detail?id=942045#c17 Which basically translates, if this is added to spec, then it can be added to Chrome. And I fully understand the team's position, being that it's better to see if W3C can reach a consensus how it can be implemented, and then implement it into the browser. I'm assuming they want to avoid adding something proprietary like Apple did. -- GitHub Notification of comment by clshortfuse Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3708#issuecomment-492346174 using your GitHub account
Received on Tuesday, 14 May 2019 18:05:26 UTC