Skip to content

[css-fonts] Add a ui-sans-serif keyword to go with ui-serif #4468

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
AmeliaBR opened this issue Oct 29, 2019 · 2 comments
Closed

[css-fonts] Add a ui-sans-serif keyword to go with ui-serif #4468

AmeliaBR opened this issue Oct 29, 2019 · 2 comments

Comments

@AmeliaBR
Copy link
Contributor

A follow-up to #4107:

In that issue we agreed to add ui-serif, ui-monospaced, and ui-rounded to allow access to variants of system fonts other than the standard system-ui font. However, this set of names assumes that system-ui is a sans-serif style, which may not always be true.

There should be a ui-sans-serif keyword for authors who want to specifically request the system's sans serif style. The system-ui keyword would continue to be the primary font used by the system interface, regardless of style. These two keywords might map to the same font; the difference is in intent.

@Crissov
Copy link
Contributor

Crissov commented Oct 30, 2019

The result of the discussion in #4397, which is about Nastaliq and styles or hands of other non-European scripts, should probably also inform the decision which UI fonts should be accessible through CSS, and perhaps voice versa (re rounded).

@css-meeting-bot
Copy link
Member

The CSS Working Group just discussed [css-fonts] Add a ui-sans-serif keyword to go with ui-serif, and agreed to the following:

  • RESOLVED: add ui-sans-serif
The full IRC log of that discussion Topic: [css-fonts] Add a ui-sans-serif keyword to go with ui-serif
GitHub: https://github.com//issues/4468
AmeliaBR: With the new ui- font family keywords. Based on the resolution, we had ui-serif, ui-monospace, and ui-rounded keywords. ui-sans-serif wasn't initially added because the system ui fonts of current systems are all sans-serif, so we didn't need a new keyword
q+
AmeliaBR: Logically there's nothing in system-ui that says it must be sans-serif, and in the future, system-ui might be serif. A more logical system would have ui-sans-serif keyword, so if you care about it, you can specify it explicitly, vs system-ui gives you the default system font regardless of its styling. In most systems these would map to the same font
chris: I agree it's currently not like that, but it could change in the future
chris: I agree with this suggestion
+1 to proposal
chris: We've already clarified that these names can all point to the same thing
myles: Mildly against this just because it's building infrastructure for a computer that doesn't exist
astearns: I can see the future possibility, we coudl add the additional keyword when it becomes necessary.
chris: But people will use it in the interim to mean sans-serif will be surprised.
astearns: I'm not sure people aren't already going to make that assumption regardless of another keyword
fantasai: But this means they ahve to make that assumption
chris: It lets authors be more precise
fantasai: If we don't add this, then they have to make the assumption. If we add this keyword, they don't have to
astearns: I'm not strongly opposed to adding it
plinss: I have slippery slope concerns here. It sounds like we're re-inventing things we had in the 90s.
AmeliaBR: We've already made the agreement on adding a set of stylistic system fonts. Do we acknowledge that system-ui is by default a sans-serif, or do we include a sans-serif in a stylistic set of keywrods
chris: The people arguing against this are arguing against the keywords in the first place
plinss: I don't think it should be serif or sans-serif
chris: Yes, system-ui shouldn't include that. But we've already got ui-serif and ui-monospaced. Those are 2 of the generic font families. I don't think anyone is asking for more
plinss: People will ask for stylistic, semantic implications, one being used for body text or headings ... again, it seems like it's going to get out of hand. Not a strong objection, I'm just concerned
chris: I can understand that.
Note, it's ui-monospace not ui-monospaced now
astearns: I'm not a big fan of ui-serif and ui-monospace, but we have decided to add them, and I'm somewhat convinced by the argument that, since we have ui-serif, we should also have ui-sans-serif to future-proof
astearns: We shouldn't have ui-serif in the first place. The connotations of what it means will change over time. I don't see how that's getting you anything
plinss: ui-monospace has a functional difference.
s/astearns: We shouldn't have/plinss: We shouldn't have/
astearns: Does anyone want to really object? Or shall we put it in for now?

I think given we have ui-serif/ui-rounded/ui-monospace, I think it's important to have ui-sans-serif
astearns: The proposal is to add ui-sans-serif (as a sibling to ui-serif)
astearns: Sounds like we're leaning toward it.
astearns: Objections?
plinss: I'd like to reconsider ui-serif
astearns: Oh, certainly, we can re-litigate adding the pair of them, but if we have one, the proposal is we should have the other.
plinss: I agree.
chris: Do these set size and style as well?
AmeliaBR and myles: no
RESOLVED: add ui-sans-serif

litherum added a commit to litherum/wpt that referenced this issue Nov 23, 2019
foolip pushed a commit to web-platform-tests/wpt that referenced this issue Nov 28, 2019
moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this issue Dec 5, 2019
… a=testonly

Automatic update from web-platform-tests
[css-fonts] Add tests for ui-sans-serif (#20415)

As per w3c/csswg-drafts#4468
--

wpt-commits: 1e9199f75fae376a4ced1d322c34b0dc7eb670b6
wpt-pr: 20415
xeonchen pushed a commit to xeonchen/gecko that referenced this issue Dec 5, 2019
… a=testonly

Automatic update from web-platform-tests
[css-fonts] Add tests for ui-sans-serif (#20415)

As per w3c/csswg-drafts#4468
--

wpt-commits: 1e9199f75fae376a4ced1d322c34b0dc7eb670b6
wpt-pr: 20415
bhearsum pushed a commit to mozilla-releng/staging-firefox that referenced this issue May 1, 2025
… a=testonly

Automatic update from web-platform-tests
[css-fonts] Add tests for ui-sans-serif (#20415)

As per w3c/csswg-drafts#4468
--

wpt-commits: 1e9199f75fae376a4ced1d322c34b0dc7eb670b6
wpt-pr: 20415
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants