Closed CarlBeek closed 1 year ago
This is related to #119 right? I just noticed that the console errors were caused by a server configuration (checkout this answer).
I just added the woff2 and otf file types and it seems that the console errors dissapeared. I couldn't replicate the bug in #119 but I have the feeling that it might be related to network connection.
To hide the text input and avoid browsers asking to save the field as password, we decided to use a custom font family "text-security-disc". It may take a couple of seconds to change between font families if the connection is slow.
Yup, I agree #119 could be the result of issues. Thanks for adding the file types. Closing this for now. 👍
It appears there is something wrong with the font being imported. In particular, there appears to be a decoding error:
Firefox console:
Chrome console: