You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently browser backend can't reference system installed fonts, as browser doesn't allow such access.
Apparently, new web standard of Local Font Access API attempts to bring this access, but as per usual with all new standards - it's only supported by chromium.
Still it's worth to investigate and try using with Avalonia.
On a related note: Here is a discussion about the theoretical implementation in Firefox (the actual standard is written by Google), which should give at least a vague indication about if this will be ratified into a proper web standard supported by non Chromium browsers.
In any case, I am not sure it's a good idea to implement this yet. While Chromium is very popular it has a lot of competition, especially on mobile from web kit (although that may change soon thanks to Europe). I suspect the number of issues people will raise about fonts not working properly on all devices/browsers will be higher than the ones this would solve.
Is your feature request related to a problem? Please describe.
Currently browser backend can't reference system installed fonts, as browser doesn't allow such access.
Apparently, new web standard of Local Font Access API attempts to bring this access, but as per usual with all new standards - it's only supported by chromium.
Still it's worth to investigate and try using with Avalonia.
Describe the solution you'd like
See https://developer.mozilla.org/en-US/docs/Web/API/Local_Font_Access_API
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: