Welcome to the Bug Reporting page! Please refer to these tips when submitting new bug reports:
1. Browse the known issues section or check if another user previously posted about a similar issue.
2. Upvoting posts help us understand how many players are experiencing the bug.
3. Refer to the Best Practices to learn how to write a bug report.
4. File each issue separately if you’ve encountered multiple issues.
1. Browse the known issues section or check if another user previously posted about a similar issue.
2. Upvoting posts help us understand how many players are experiencing the bug.
3. Refer to the Best Practices to learn how to write a bug report.
4. File each issue separately if you’ve encountered multiple issues.
Problems with Reviewing display due to posible failure in updating it
GuyFawkesGreen-PGO
Posts: 22 ✭✭
in Report a Bug
So I was up to made some reviews today as usual, and came with the surprise that Wayfarer changed the disposition of the reviewing sections, but with failures in the displaying of figures (stars, arrows, and so on), making it difficult to review. Is it part of the massive updating they've been announcing?
Nominations tab has the same issue.
Browser is Mozilla Firefox. There seems to be no issue reviewing from phone
Comments
Update:
It seems it's only Mozilla Firefox the browser with the issue.
Google Chrome seems to work as usual
As of 1 year ago, issue hasn't been resolved yet.
Still cannot review from Firefox.
I can review fine on Firefox. Maybe you have an add on or extension that's breaking the site?
It most certainly is about the font. Some font families don't have symbol or icons that represent what it's saying (i.e. star_outline, keyboard_arrow_down) or it's the theme currently in Mozilla that is not allowing such images/symbols to load.
Here's one thing that might be blocking such images. Agree with Wolfman, see what extensions you might have.
When I reverted the font to the original, the issue was indeed fixed. So the problem was with the font.
What is worth to call out is that when I used the custom font before the update made to the interface 1 year ago, there weren't any problems with the icons; therefore the font bug arose with that update.