- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 05 Nov 2021 17:26:06 +0000
- To: public-css-archive@w3.org
Wrt info discovery, there's not a lot we can do if you're not setting up the `unicode-range` properly. Allowing that to work would encourage writing pages that trigger multiple useless font downloads before we finally discover one that works, which is a bad user experience. But if you *do* write `unicode-range` to cover the actual characters of the font, then the [`FontFaceSet.check()`](https://drafts.csswg.org/css-font-loading/#font-face-set-check) method *somewhat* works. It's not *designed* for this use-case, but you can finagle it, by creating a dummy font that's not loaded with a default (full-coverage) unicode-range, and putting its name last in the `.check()` list, so *if* it falls back to that font due to bad character coverage, the method will return `false`. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6798#issuecomment-962079873 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 5 November 2021 17:26:07 UTC