engaging-computing / engaging-computing/MYR

text() doesn't always render properly.

Open
#467 0 comments 0 reactions 0 assignees View on GitHub
a-frame bug Frontend Minor bug
Dominant language
JavaScript
Stars
24
Forks
22
PR merge metrics
No merged PRs in 30d

Description

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](https://user-images.githubusercontent.com/50585524/112740918-c2010580-8f4e-11eb-83e0-65de855a40a4.png)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.