Skip to content

[css-fonts] Should we start a registry for additional generic fonts? #827

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.

Sign up for GitHub

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

Jump to bottom
Open
xfq opened this issue Dec 6, 2019 · 1 comment
Open

[css-fonts] Should we start a registry for additional generic fonts? #827

xfq opened this issue Dec 6, 2019 · 1 comment
Labels
i:fonts Fonts & font styles s:css-fonts https://drafts.csswg.org/css-fonts/ tracker i18n is following a discussion, but doesn't require resolution. wg:css https://www.w3.org/groups/wg/css

Comments

@xfq
Copy link
Member

xfq commented Dec 6, 2019

This is a tracker issue. Only discuss things here if they are i18n WG internal meta-discussions about the issue. Contribute to the actual discussion at the following link:

§ w3c/csswg-drafts#4566
@xfq xfq added tracker i18n is following a discussion, but doesn't require resolution. s:css-fonts https://drafts.csswg.org/css-fonts/ i:fonts Fonts & font styles labels Dec 6, 2019
@himorin
Copy link
Contributor

himorin commented Dec 12, 2019

Short summary: whether to have registry but not rec-type spec for listing font names like named local fonts

@w3cbot w3cbot added the wg:css https://www.w3.org/groups/wg/css label Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
i:fonts Fonts & font styles s:css-fonts https://drafts.csswg.org/css-fonts/ tracker i18n is following a discussion, but doesn't require resolution. wg:css https://www.w3.org/groups/wg/css
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@xfq @himorin @w3cbot