Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

text() doesn't always render properly. #467

Open
samuel-zuk opened this issue Mar 28, 2021 · 0 comments
Open

text() doesn't always render properly. #467

samuel-zuk opened this issue Mar 28, 2021 · 0 comments
Labels
a-frame bug Something isn't working Frontend Issues being caused via the frontend Minor bug

Comments

@samuel-zuk
Copy link
Contributor

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.

ASCII text renders, non-ASCII text doesn't

@samuel-zuk samuel-zuk added bug Something isn't working a-frame Frontend Issues being caused via the frontend Minor bug labels Mar 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a-frame bug Something isn't working Frontend Issues being caused via the frontend Minor bug
Projects
None yet
Development

No branches or pull requests

1 participant