If users install fonts in the obvious way they are likely to be installed in the user profile on the path ~/Library/Fonts
Since browsers are sandboxed but vscode isn't, that means vscode can use them but the browser can't, and therefore Print can't. So much for Apple's "it just works" baloney.
When the extension starts it should check for fonts installed in the user profile that aren't in system fonts. When this list isn't empty it should offer to repair. Repair in this case means put the fonts in the system font folder.
If users install fonts in the obvious way they are likely to be installed in the user profile on the path
~/Library/FontsSince browsers are sandboxed but vscode isn't, that means vscode can use them but the browser can't, and therefore Print can't. So much for Apple's "it just works" baloney.
When the extension starts it should check for fonts installed in the user profile that aren't in system fonts. When this list isn't empty it should offer to repair. Repair in this case means put the fonts in the system font folder.