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

We (@dbaron @hober @plinss) looked at this again during the TAG F2F this week. We've tried to file issues in the WICG/local-font-access repo which capture each of the concerns that have come up during the several TAG breakouts on these two reviews. Given the lack of engagement in these reviews thus far, we don't see any value in keeping these issues open. Please feel free to ping us to re-open or file a new issue when there are significant changes.

* [Non-OpenType fonts #19](https://github.com/WICG/local-font-access/issues/19)
* [Anne's feedback re: Non-goals and alternative approaches #20](https://github.com/WICG/local-font-access/issues/20)
* [Fonts need to be sorted #23](https://github.com/WICG/local-font-access/issues/23)
* [mention additional fingerprinting surface in details of font versions #25](https://github.com/WICG/local-font-access/issues/25)
* [Please add a Table of Contents to the explainer #26]()
* [explainer suggests iterating all the fonts in order to find Consolas #27](https://github.com/WICG/local-font-access/issues/27)


-- 
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/400#issuecomment-634347782