Timeline for Using Safari 5.1.4, code blocks are empty on Stack Overflow
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 28, 2012 at 20:14 | history | edited | Arjan | CC BY-SA 3.0 | Note about 5.1.5 |
| Mar 23, 2012 at 4:51 | comment | added | Glyph | Thank you for this. Never would have guessed in a hundred years. I don't even remember why I would have ever set 32-bit mode in the first place :). | |
| Mar 19, 2012 at 19:03 | comment | added | user181619 | Was running in 32-bit, Lion, I think because of Slingbox Player. Resetting Safar to run 64 bit worked for me. | |
| Mar 17, 2012 at 12:15 | vote | accept | user1040049 | ||
| Mar 16, 2012 at 20:18 | comment | added | Arjan | No issue in Safari 5.1.4 on a 32-bit 2006 Snow Leopard Mac (nor in some older version, which I did not correctly write down). I do not see web sockets being used in the Safari's Web Inspector's console log (like I do in Safari on Lion). Safari does support web sockets on 32 bit, but SE does not seem to use it? (On Chrome, WebSocket yields function WebSocket() { [native code] }, but in Safari it's WebSocketConstructor. However, that's the same on 64-bit, so I doubt that matters.) (ping @balpha, FYI.) | |
| Mar 16, 2012 at 18:16 | comment | added | Robusto | Bravo, fixed my problem! | |
| Mar 16, 2012 at 10:47 | history | edited | Alex Reynolds | CC BY-SA 3.0 | added 233 characters in body |
| Mar 16, 2012 at 9:53 | comment | added | Arjan | Actually, the code disappears when the web socket for the notifications is opened. Until then, all is fine. I will fire up an old Mac that doesn't support 64-bit to start with. To be continued, @balpha. | |
| Mar 16, 2012 at 9:47 | history | edited | Arjan | CC BY-SA 3.0 | Added image to make the solution stand out. |
| Mar 16, 2012 at 9:42 | comment | added | Arjan | Yes, I can confirm your 32 bit mode problems. In that case, I very clearly see the code on page load, but disappear right away. (That solves this, @balpha, I guess.) | |
| Mar 16, 2012 at 8:26 | history | edited | Alex Reynolds | CC BY-SA 3.0 | added 329 characters in body |
| Mar 13, 2012 at 13:58 | comment | added | balpha StaffMod | In the future, please just post bug reports like this here on meta. We like to be shamed publicly :) | |
| Mar 13, 2012 at 10:20 | comment | added | Alex Reynolds | It looks like Apple made some major changes with the new JS engine. It's "cutting edge" in that sense, definitely. But to answer Arjan's question: no, there are no errors reported in the Console. | |
| Mar 13, 2012 at 7:14 | comment | added | CharlesB | Safari 5.1.4 is stable release, so I wouldn't call this "cutting edge"... | |
| Mar 13, 2012 at 7:00 | comment | added | Arjan | Any JavaScript errors in the Web Inspector's Console tab? | |
| Mar 13, 2012 at 5:41 | history | answered | Alex Reynolds | CC BY-SA 3.0 |