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: jfkthame via GitHub <sysbot+gh@w3.org>
Date: Thu, 15 Oct 2020 17:11:44 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-709467433-1602781903-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.

There's a trade-off between privacy and functionality here; we all realize that. The functionality involved is sometimes purely a matter of aesthetics, but other times it may make the difference between a user being able to read a page or not. While a user agent may make various choices with regard to *default* behavior, it seems severe for a *user* agent to entirely block functionality that may be critical to the usability of web pages the user wants to see.

Florian's proposed text uses *should* rather than *must*, so it does not impose a mandatory requirement on UAs, but I think it sends a worthwhile signal about the importance of this issue.

-- 
GitHub Notification of comment by jfkthame
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/5625#issuecomment-709467433 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:11:47 UTC

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