Re: [w3ctag/design-reviews] Font Enumeration API (#399)

I wrote [in December 2019](https://github.com/w3ctag/design-reviews/issues/399#issuecomment-561387155):

> @plinss and I[...] share @dbaron’s & @ylafon’s desire for a "less-powerful APIs that could address [some of] the same use cases"—in particular, a picker-style API could allow sites to receive access to specific fonts that they need (like Consolas in the previous example) without exposing the list of installed fonts.
> 
> @plinss remembers a TPAC conversation from Fukuoka, perhaps in the Houdini TF, where a picker-style API got significant support.

We still believe that a picker-style API solves the most pressing user needs while having far preferable characteristics re: privacy, which we've documented in our [Web Platform Design Principles](https://w3ctag.github.io/design-principles/) document (specifically in [8.2. Use care when exposing APIs for selecting or enumerating devices](https://w3ctag.github.io/design-principles/#device-enumeration)).

Note that such an approach would also address WICG/local-font-access#36 and WICG/local-font-access#62.

From [this comment](https://github.com/WICG/local-font-access/issues/62#issuecomment-759620208) it looks like you're considering a picker-style API alternative. We look forward to learning more about it.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/399#issuecomment-767195003