Using Safari 5.1.4, code blocks are empty on Stack Overflow

Question

Code blocks on Stack Overflow (lines beginning with 4 whitespaces) with Safari v5.1.4 are empty/blank (even with the inspector, indicating it's populated via javascript). If I use another browser (i.e. Chrome), they have content.

Using the same browser (Safari v5.1.4) on another Stack Exchange site, say Server Fault, doesn't have the same problem.

Since Safari v5.1.4 was just released, it's very possible it could be a problem with the browser. But given the fact that two sites from Stack Exchange are showing different behaviour, I'd suspect the website at this point.

My browser is vanilla (no extensions/plug-ins).

Can others confirm this?!

When viewing the question NSregularExpression and password I get the following warning (but I don't believe it's related):

pixel;r=627855533;a=p-c1rF4kxgLUzNc;fpan=0;fpa=P0-1610253758-1313464351283;ns=0;ce=1;je=1;sr=1680x1050x24;enc=n;dst=1;et=1331643039578;tzo=240;ref=http%3A%2F%2Fstackoverflow.com%2F;url=http%3A%2F%2Fstackoverflow.com%2Fquestions%2F9683656%2Fnsregularexpression-and-password;ogl=:-1
Resource interpreted as Image but transferred with MIME type text/plain.

Answer 1

I reported the same issue via the 'contact us' link at the bottom of Stack Overflow. I haven't gotten a response, but I imagine they are working on it. When you work on the cutting edge, expect blood! :)

I quit Safari and looked at its info window in the Finder. It was in 32-bit mode (I set it as 32-bit for some reason which escapes me at the present moment). I restarted Safari in 64-bit mode and it appears that this helped fix the code block issue. Can someone else try this out and see if they see the same fix?

The Safari 5.1.5 release notes state "Safari 5.1.5 contains a fix for an issue that could affect website usability when running Safari in 32-bit mode" so that hopefully fixes this for those who need 32-bit mode.

(Thanks to Macintouch readers for providing the inspiration to try out this mode change. This also appears to fix other issues with Safari 5.1.4.)

Answer 2

I could constantly reproduce the problem, even after re-launching Safari.

In the comments above, Arjan mentioned the exact same build numbers I had, mentioned he also hadn't rebooted and couldn't reproduce the issue. This made me try to reboot... and now it's resolved.

I feel somewhat sheepish now! Rebooting might sound obvious to some but from where I'm standing, having to reboot is the exception.

Edit: Premature celebration. The issue is back. I'll try to figure out how to better reproduce it.

Answer 3

Declining this but as it seems to be a quirk with Safari and not the site.