Couple of sites will not display any of it's text only graphic elements and table structures
I have a couple of sites that I can not view any text in Firefox 68.9.0esr (64bit) (and earlier) on a Debian Buster 10 LXDE system. two examples. www.ups.com and www.tuxmachines.org Both work fine in Epiphany browser on same unit and seem to work fine in a number of other units including another Debian 10 based unit. So it is probably a Debian Buster configuration issue on my unit, but any help in what to look for would be helpful. When navigating to the UPS landing page normally you get a map of world and a menu down right hand side with list of countries. I only get the graphic elements displayed, not of the actual text is rendered. Similar with www.tuxmachines.org, all the graphic elements are displayed but all of the text is hidden, looking in page source you can see the text is present. Likewise if you receive an email from UPS the message body is largely blank because the text is all hidden in the html they send, but appears fine in the Claws email agent. Where or what to look for? Could it be font(s) related? I've tried clear cache and restarting in safe mode, same effect. k.
Valgt løsning
You can check the Web Console (Tools -> Web Developer) for messages about blocked content and about the presence of mixed or unsafe content.
You can check the Network Monitor to see if content is blocked or otherwise fails to load.
If necessary use "Ctrl+F5" or "Ctrl+Shift+R" (Mac: Command+Shift+R) to reload the page and bypass the cache to generate a fresh log.
You can right-click and select "Inspect Element" to open the builtin Inspector with this element selected.
You can check in the Rules tab in the right panel in the Inspector what font-family is used for selected text. You can check in the Font tab in the right panel in the Inspector what font is actually used because Firefox might be using a different font than specified by the website.
Læs dette svar i sammenhæng 👍 1Alle svar (2)
Valgt løsning
You can check the Web Console (Tools -> Web Developer) for messages about blocked content and about the presence of mixed or unsafe content.
You can check the Network Monitor to see if content is blocked or otherwise fails to load.
If necessary use "Ctrl+F5" or "Ctrl+Shift+R" (Mac: Command+Shift+R) to reload the page and bypass the cache to generate a fresh log.
You can right-click and select "Inspect Element" to open the builtin Inspector with this element selected.
You can check in the Rules tab in the right panel in the Inspector what font-family is used for selected text. You can check in the Font tab in the right panel in the Inspector what font is actually used because Firefox might be using a different font than specified by the website.
Thankyou, by combining this with font-manager in Debian, "we" resolved this. I couldn't see any blocked content in Console or Network Monitor On trying to inspect element. I couldn't see the Rules tab in the right hand panel. But some other aspects especially in the Fonts section was enlightening. In the central pane, the "inherited from body" has list of fonts in the first and third "body" sections In the first it has a list with Tahoma first and underlined, hovering over any of these fonts is blank popup But when you hover over the fonts listed in the third body these fonts do show sample text in the popup. And in the right pane under the "All fonts on page" section the Tahoma fonts are blank but the other fonts have samples.
and if I load font-manager from terminal I see messages like this in the terminal window (font-manager:2361): Pango-WARNING **: 17:04:46.374: font_face status is: <unknown error status> (font-manager:2361): Pango-WARNING **: 17:04:46.374: scaled_font status is: out of memory (font-manager:2361): Pango-WARNING **: 17:04:46.374: shaping failure, expect ugly output. shape-engine='PangoFcShapeEngine', font='Tahoma 69.9990234375', text='The quick brown fox jumps over the lazy dog.'
If I disable the font in font-manager, update the font cache and restart firefox all looks good.
So, purely out of interest. 1. Why does firefox try to default/use Tahoma (or is that a Debian question)? 2. Why does epiphany not have an issue?
