New York Times web page corrupted
In the last month the New York Times site has had consistent problems where pages display as unprintable characters on a white background. This occurs at random but frequently on pages throughout the site, as well as on the main page. This does not seem to be limited to Firefox, but it is much worse than with other browsers, including Chromium (linux) as well as Safari and Atomic on iPad.
The NYT support claims support on IE only and does not feel it's their problem.
Alle Antworten (5)
Can you attach a screenshot?
- http://en.wikipedia.org/wiki/Screenshot
- https://support.mozilla.org/kb/how-do-i-create-screenshot-my-problem
Use a compressed image type like PNG or JPG to save the screenshot.
Such issues can be caused by a problem with the font that is used to display the text.
You can use this extension to see which fonts are used for selected text.
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"
This is not a font issue. Screenshot attached.
Try to Reset Firefox. Refresh Firefox - reset add-ons and settings
You can check the network.http.* prefs on the about:config page and reset all bold user set network.http prefs to the default value via the right-click context menu -> Reset.
Check at least:
- network.http.accept-encoding (default: gzip,deflate)
- http://kb.mozillazine.org/network.http.accept-encoding
You may still need to clear the cache and the cookies from sites that cause problems or reload and bypass the cache via Ctrl+F5.
"Clear the Cache":
- Tools > Options > Advanced > Network > Cached Web Content: "Clear Now"
"Remove Cookies" from sites causing problems:
- Tools > Options > Privacy > Cookies: "Show Cookies"
Geändert am von cor-el
A general reset seems to have resolved the problem, though it will take a while to be sure. This seems like a pretty big hammer to use.
I would have tried the about:config, but the general reset was already underway.
Thanks for the help.