[Mac triage] Unfortunately, this bug tracker isn't for web features — just Chrome and its implementation of those features. The w3c and WHATWG maintain the specs, and I *believe* that these days they use GitHub repos as a sort of alternative to mailing lists to discuss spec changes:

https://github.com/w3c/
https://github.com/whatwg/

The HTML repo might be the best place to ask about this (https://github.com/whatwg/html).

This may not have come up because most web apps provide their own fonts instead of letting the user choose a local font to avoid issues with, say, creating a document on one machine and then opening it on another machine without that font. But, I realize that it may still be desirable to let users pick a local font in your case.

For what it's worth, I'd bet that an API to list a user's fonts would be met with resistance because it could be used for fingerprinting, but an <input type=font> that lets the user choose a font from a browser-provided dialog might be less scary.

Thanks for the feedback and the links. Will try my luck over there.
Somewhere I still do not understand it. I mean Google is pushing for
Web based apps, but than, why don't provide the tools todo so ?

But thanks anyway :)

I have submitted https://github.com/whatwg/html/issues/3379. Let's see what happens.

> Somewhere I still do not understand it.

There are computers, like Chromebooks, which *only* have a web browser — there is no way to install fonts locally.

The "web" way is for your app to provide some fonts of its own and a way for the user to add their own fonts to the app. Then it would be useful on any computer with a web browser.

Yes ok, I understand. And we will probably go this route when we need the curve info from the fonts for 3D rendering.

However for 2D. Designers have hundreds of fonts installed locally. They would not be satisfied with a small list of fonts. Again, we try to compete with something like Photoshop in the browser. Apart from that, most fonts are copyrighted and it would be a licensing nightmare to provide these to the user somehow all on our own. Especially as the user could actually already use this font in the 2D canvas if he only enters the name of the font into the dialog (the way we do it right now), however doing it this way without a font dialog is certainly not user friendly.

But thanks anyway for listening :)

No problem, and I see where you're coming from too. I'm watching the GitHub issue :-).