Re: [w3ctag/design-reviews] Font Table Access API (#400)

The issues as we see them so far:
  
  1. there are a number of unresolved issues which have been raised during the course of this review (e.g. [#19](https://github.com/WICG/local-font-access/issues/19), [#20](https://github.com/WICG/local-font-access/issues/20), [#62](https://github.com/WICG/local-font-access/issues/62), etc.)
  2. the fingerprinting risk is quite large here. There's always a tradeoff to be made regarding fingerprinting surface area and new functionality - however in our view the high risk is not commensurate with the benefit in this case.
  3. the API seems to be on a trajectory to ship regardless of our feedback and the other negative feedback surfaced on this issue.

In conclusion: we think we should be more deliberate as stewards of the web platform in terms of how we represent fonts.  We don't think this is the right approach to solve these use cases in the context of the wider web.

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

Message ID: <w3ctag/design-reviews/issues/400/1215333348@github.com>