We refer to a lot of Apple support pages (such as), and recently some of us started seeing them appear garbled, with overlapping characters in the title, and rendered weirdly such that we sometimes had to scroll right even to see the text at all. This didn’t happen to everyone, and it could occur (in slightly different ways) in all three major Web browsers: Safari, Google Chrome, and Firefox. Even more confusing, some of us had the problem in Safari but not in Chrome, whereas others saw it in Chrome but not Safari. Maddening!
Although the problem was clearly related to CSS changes on Apple’s part, we couldn’t figure out why it bit different people in different browsers. And then Michael Cohen came across a tip on that was the key we needed to solve it, even if we still can’t explain precisely why it’s happening.
The tip Michael found pointed out that the problem could be eliminated in Safari with a particular setting. Just open Safari > Preferences > Advanced and deselect “Never use font sizes smaller than.” It’s quite striking — just toggling that checkbox while that page is open reformats it completely.
Problem solved, at least for Safari. What about Firefox? Mozilla’s Web browser has nearly the same option, found by choosing Firefox > Preferences, clicking Content in the left-hand sidebar, and then clicking the Advanced button next to Fonts. In that dialog, there’s a pop-up menu for Minimum Font Size; set it to None and the problem with Apple support pages disappears as soon as you click OK.
On to Chrome. Solving the problem here was more work, since although Chrome has font-related settings, it lacks an equivalent to the option in Safari and Firefox that prevents Web pages from using too-small fonts.
On a hunch, I pulled my Chrome folder out of
~/Library/Application Support/Google and was rewarded by the problem going away on the app’s next clean-slate launch. I can’t identify everything in that folder, but since I didn’t want to lose bookmarks, history, and who knows what else, I instead channeled the venerable Conflict Catcher from System 7 days.
After making a backup for safety, I first deleted half the items in the Chrome folder, relaunched Chrome, and tested a broken page. When the problem didn’t go away, I knew it must be related to something in the other half of the files, so I quit Chrome, pressed Command-Z to undo the trashing of the first half of the files (the Finder helpfully overwrote the new files Chrome had created), and repeated with the other half. The problem went away then, so I kept testing with ever-smaller sets until I’d narrowed the problem to a single file. Perhaps not surprisingly, it was a file inside the Default folder called Preferences.
Looking inside that file with BBEdit didn’t reveal any settings that sounded related, so I tossed it, relaunched one last time, and Apple support pages started to render properly. So if you’re running into this problem with Chrome, delete
Unfortunately, Chrome then had other issues: favorites and extensions were both missing. Fixing that was easy, but only because I use Chrome’s option for syncing data with my MacBook Air. When you sign in to Chrome using your Google account on two machines, you’re given the option to sync any or all of apps, autofill entries, bookmarks, extensions, history, passwords, settings, themes, and open tabs. To sign in, click the silhouette in the upper-right corner of Chrome’s window, and enter your Google password. That put everything back for me, albeit with some two-factor authentication dancing. The moral of the story is not to delete anything from Chrome until you’ve enabled syncing and ensured that all your data is stored in your Google account.
All that was left was going through my Chrome extensions and enabling those I actually use, which revealed two extension-related quirks. First, Hitlist’s
talkgadget.google.com to the now-erased
list of exceptions for sites that I allow to load third-party cookies.
So, if Apple’s support pages are garbled for you too, you can now fix the problem with ease in Safari and Firefox, and with a bit of elbow grease in Chrome.