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
I've ran into two issues with text() recently: non-ASCII characters passed to text() don't render, and if third party scripts/requests are disabled, text does not render at all (including the text used to display grid axis labels).
This bug is caused because the font used by default for text only contains ASCII characters-- this can be fixed by hosting a modified version of the default font (Roboto) ourselves. We'd need to include at least some basic Unicode symbols, such as accented vowels and the like. This will also fix the issue with third-party scripts and/or requests, since A-Frame loads the fonts used to render the text over their CDN.
I've ran into two issues with text() recently: non-ASCII characters passed to text() don't render, and if third party scripts/requests are disabled, text does not render at all (including the text used to display grid axis labels).
This bug is caused because the font used by default for text only contains ASCII characters-- this can be fixed by hosting a modified version of the default font (Roboto) ourselves. We'd need to include at least some basic Unicode symbols, such as accented vowels and the like. This will also fix the issue with third-party scripts and/or requests, since A-Frame loads the fonts used to render the text over their CDN.
See here: https://aframe.io/docs/1.2.0/components/text.html#stock-fonts.
The text was updated successfully, but these errors were encountered: