fixedsys font in options causes unreadable text on page
Running Firefox 52.0esr on pre-Win7 platform and seeing unreadable text. Here are some examples: a web page (https://www.gnu.org/software/coreutils/manual/html_node/kill-invocation.html) showing unreadable text and the view source display also partly unreadable - see 4 attachments. Some images show correct look versus incorrect look.
It took me a while to track this down to a change I made many years ago. I changed the options in Firefox for Monospace font to "Fixedsys" font (Tools|options|content| Fonts&colors, advanced). I had no problems (up to v25 and few latter versions) until I updated to Firefox 52.0esr. The solution is to change fonts, Courier New, seem to work fine now. I wrote this up in case anyone else comes across the issue as it is not that obvious when "Monospace font" applies the only clue that helped me solve it was when view source was garbled then I knew it was not a web page coding problem.
I am on a non-supported platform BUT is this a problem on Win7 and higher + Firefox 52 and higher or is just a quirk specific to my setup?
Modified by Scott
All Replies (2)
Hi, unfortunately your info above will not be seen by anyone. These have to be made solved before the public actually sees it in a google search.
As for XP/VISTA yes it is unsupported after Sept 5th. 52.9.0esr is the last browser that is stable and secure. https://www.mozilla.org/en-US/firefox/organizations/all/#legacy if you are not one it please switch to it. But backup 1st.
- https://support.mozilla.org/en-US/kb/export-firefox-bookmarks-to-backup-or-transfer
- https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles
All browsers after 52.9.0 will be incompatible for use with XP but will be fine for Windows 7/8/10
Pkshadow said
Hi, unfortunately your info above will not be seen by anyone. These have to be made solved before the public actually sees it in a google search.
That seems a strange policy for a support site.
Was that a generic reply?
Just to clarify I am asking if this problem has been fixed on current Firefox on windows 7. I already know exists in the older version, and is easy enough to test for in current version. That is likely the next platform I will use.
Modified by Scott