Skip to content
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

Add CSSWG issue link #4

Open
astearns opened this issue Feb 18, 2020 · 3 comments
Open

Add CSSWG issue link #4

astearns opened this issue Feb 18, 2020 · 3 comments

Comments

@astearns
Copy link

w3c/csswg-drafts#4497 seems more appropriate than "No signals"

@jyasskin
Copy link
Member

Thanks for finding a good link. Can you, perhaps, provide a short summary of the WG's current opinion so people reading the explainer don't have to wade through that whole issue?

@astearns
Copy link
Author

@snyderp is working on a summary, so I would defer to him. My understanding is that we think a list-based solution should work (which would need some research and iteration to not break things for minority scripts), and that there will need to be an opt-in in browser prefs to allow local font access when it's appropriate.

@pes10k
Copy link
Contributor

pes10k commented Feb 19, 2020

@astearns thats for the ping. Here is a summary and alternate proposal I expect will solve the use cases w/ less machinery and "freeze the web" risk than the other discussed options.

#6

It would be very good to have CSSWG discussion on this repo too!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants