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

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

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Mon, 30 Nov 2020 21:56:00 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-736080077-1606773359-sysbot+gh@w3.org>
Sigh, that's annoying that nobody ever fixed to match; that spec text came from fairly early in implementation progress.  That does explain why nobody ever pinged me to fix the obvious FIXME there, at least.

This is a slightly easier method to probe for installed fonts than the existing "render a span with `font-family: "Local Font", "Weird Metrics Web Font";` and measure the size", but it's not a significant difference; the existing one can still run at approximately the browser's frame-drawing rate, or maybe half that, which is enough to run thru several hundred fonts in a handful of seconds, and entirely off-screen so the user has no idea. I don't think pursuing a change here *for the purpose of reducing this privacy hole* is a significant reason, since the gain from this API is so small relative to existing methods.

That said, I'm still comfortable going with Firefox's behavior (returning `true` when no fonts are matched at all) if browsers don't want to converge on matching the spec. (And I recognize that, at this point, changing to throwing an error would very likely be a webcompat issue, while changing from `false` to `true` for Chrome should probably be okay.)

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 30 November 2020 21:56:08 UTC

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