You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
@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.
@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.
w3c/csswg-drafts#4497 seems more appropriate than "No signals"
The text was updated successfully, but these errors were encountered: