W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2020

Re: [csswg-drafts] [css-fonts-4] Add explanatory text about tradeoffs on blocking local fonts, particularly wrt i18n considerations (#5625)

From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
Date: Thu, 15 Oct 2020 17:02:38 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-709461837-1602781357-sysbot+gh@w3.org>
> Would you have a problem tweaking this by adding something like:
> 
> > User agents that choose to make some fonts unavailable by default for privacy reasons should offer a way for users to make specific fonts available.

I would have a problem with this. It's a user agent's choice whether or not they want to allow users to opt-in to bad privacy. Also, CSS should not dictate what UI is present in the browser chrome. Adding browser UI has cost, both on the developer and the user (in the form of additional complexity) and it's up to the UA to determine if the cost is worth it.

All we can do here is make the point that some fonts might be required for i18n, and let the UA determine how best to satisfy that requirement.

-- 
GitHub Notification of comment by litherum
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/5625#issuecomment-709461837 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 15 October 2020 17:02:40 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:20 UTC