Skip to content

[css-fonts] which generic in a font-family list influences system fallback? #4562

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

Open
heycam opened this issue Dec 5, 2019 · 2 comments
Open
Labels
css-fonts-4 Current Work

Comments

@heycam
Copy link
Contributor

heycam commented Dec 5, 2019

Breaking this out from #4442:

@heycam:

Do we need to add wording about which generic, if multiple are listed, influence any implementation specific system fallback?

@jfkthame:

Presumably the first generic mentioned should be the one to influence fallback after we fall off the end of the font-family list.

Is this something we need to have a SHOULD-level statement for in the spec?

@heycam heycam added the css-fonts-4 Current Work label Dec 5, 2019
@svgeesus
Copy link
Contributor

svgeesus commented Dec 5, 2019

Yes, we need to add that wording. I agree that the first generic mentioned (regardless of whether it matched to a real font or not) is the best option, because the font stack is a priority ordered list so the first generic should most closely correspond to authorial intent.

@litherum
Copy link
Contributor

litherum commented Dec 7, 2019

the first generic method should be the one to influence fallback

I disagreed in #4442 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
css-fonts-4 Current Work
Projects
None yet
Development

No branches or pull requests

3 participants