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

Re: [csswg-drafts] [css-font-loading] FontFaceSet.check() method: reality vs spec vs privacy (#5744)

From: jfkthame via GitHub <sysbot+gh@w3.org>
Date: Wed, 02 Dec 2020 14:42:31 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-737272599-1606920150-sysbot+gh@w3.org>
Agreed, the privacy issue is minor given that it's just a quicker/easier way to do what can be done anyway via other routes (that we aren't likely to be able to do anything about, aside from the broader topic -- being explored separately -- of restricting use of system-installed fonts).

The relevant [commit](https://github.com/w3c/csswg-drafts/commit/e73686097b5699745e58c42788be17b1821aa38f) that introduced the *throw* expectation just says

> Make the check() function differentiate between 'your font faces don't exist' and 'none of your fonts will render that example text'

but doesn't point to any further background. There was a lengthy discussion recorded in [F2F minutes from 2015-05-20](https://lists.w3.org/Archives/Public/www-style/2015Jun/0246.html), but it didn't really seem very clear; there seemed to be conflicting opinions about the use cases and no real consensus on how it should behave.

I put a possible edit in https://github.com/w3c/csswg-drafts/pull/5757 for consideration.

-- 
GitHub Notification of comment by jfkthame
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5744#issuecomment-737272599 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 December 2020 14:42:33 UTC

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