Why do bug descriptions at bugzilla.mozilla.org not render even in safe mode?
Firefox has not been displaying the bug description and details at bugzilla.mozilla.org for the past few versions -- I am currently at Firefox 39 on Linux Mint 17 (Ubuntu 14.04). Only some elements render on the entire page. The comments in the thread do appear but their attributes (date, commenter's name, etc.) are missing, as are elements of the page's header and footer.
I've attached screenshots of the top and bottom of the top and bottom of a page as it appears in my browser.
What might be causing this and how can I fix it?
Solução escolhida
Did you check via the right-click context menu in the Inspector (Inspect Element) if there is text loaded and what font is used on the Font tab in case there is a problem with the font?
You can do a font test to see if you can identify corrupted font(s).
You can try different default fonts and temporarily disable website fonts to test the selected default font.
- Edit > Preferences > Content : Fonts & Colors > Advanced
- [ ] "Allow pages to choose their own fonts, instead of my selections above"
Todas as respostas (4)
Solução escolhida
Did you check via the right-click context menu in the Inspector (Inspect Element) if there is text loaded and what font is used on the Font tab in case there is a problem with the font?
You can do a font test to see if you can identify corrupted font(s).
You can try different default fonts and temporarily disable website fonts to test the selected default font.
- Edit > Preferences > Content : Fonts & Colors > Advanced
- [ ] "Allow pages to choose their own fonts, instead of my selections above"
Thanks. That's what the problem was. I uninstalled the offending font and now all is good.
You're welcome.
Can you tell us what font was causing this issue?
cor-el said
You're welcome. Can you tell us what font was causing this issue?
Fira Sans.
It's one of Google's free webfonts. I got it via Typecatcher. I just verified the cause by reinstalling it and reproducing the issue, which I then fixed by uninstalling it.