New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 535764 link

Starred by 38 users

Issue metadata

Status: Assigned
Owner:
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Feature



Sign in to add a comment

Local Font Access API

Project Member Reported by dhnishi@chromium.org, Sep 24 2015

Issue description

Change description:
A Local Font Access API gives access to local fonts installed on a user's device. This enables the development of web apps for designers that need to access and manipulate the glyphs inside of fonts.

Support in other browsers:
Internet Explorer: No signals.
Firefox: No signals.
Safari: No signals.

 
Labels: Hotlist-Recharge
This issue likely requires triage.  The current issue owner may be inactive (i.e. hasn't fixed an issue in the last 30 days or commented in this particular issue in the last 90 days).  Thanks for helping out!

-Anthony

Comment 2 by e...@figma.com, Oct 14 2015

Is support for this feature still planned soon? If there's anything I can do to help out, please let me know. This feature would make a world of difference for us!

Comment 3 by ashlaa...@gmail.com, Nov 16 2015

Found this from WICG where I separately proposed the same thing: http://discourse.wicg.io/t/api-to-get-list-of-available-fonts/1197
The proof-of-concept JS font detector could be used as a polyfill: https://dl.dropboxusercontent.com/u/15217362/getfontlist.html

Comment 4 by behdad@chromium.org, Feb 17 2016

Cc: js...@chromium.org behdad@chromium.org drott@chromium.org e...@chromium.org kojii@chromium.org
Owner: owe...@chromium.org

Comment 6 by p...@figma.com, Mar 21 2016

In reply to #3, at Figma we require the actual font file vector data, not just a list of names or bitmap renderings. Figma includes a WebGL vector rendering engine. Some details are here: https://medium.com/figma-design/building-a-professional-design-tool-on-the-web-6332ed4f1fcc

Comment 7 by owe...@chromium.org, Sep 12 2017

Labels: migrated-launch-owp Type-Task
This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues.

We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate.

For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit

For any questions, please contact owencm, sshruthi, larforge

Comment 8 by laforge@google.com, Mar 15 2018

Cc: dft@google.com
Hey Owen/ Doug,

What would you recommend for next steps on this issue?

Comment 9 by laforge@google.com, Mar 15 2018

Cc: -dft@google.com dougt@chromium.org
Owner: ----
Status: Available (was: Assigned)
We stalled on this original proposal as of a few years ago.

If someone wants to take this forward I'd suggest carefully determining the requirements and then talking with eae@ about potential options.
Cc: jsb...@chromium.org
Owner: e...@chromium.org
Labels: -Pri-2 Proj-Fugu Pri-1
Labels: M-77 Target-74
Status: Assigned (was: Available)
Labels: Type-Feature

Sign in to add a comment