Safari 3.1: Debug Mode not working?
This is an open discussion with 4 replies, filed under Troubleshooting.
Search
-
-
- Alistair
- 20 Mar 08, 8:02 am
- Comment #2
yeah, you're right. That's a pain. Any ideas Scott?
-
-
- rawb
- 20 Mar 08, 8:38 am
- Comment #3
It's working fine for me (if we are talking about the page at /?debug) using Safari 3.1.
-
-
- Scott
- 20 Mar 08, 1:14 pm
- Comment #4
How very annoying. Does anyone know if Apple publishes in advance which WebKit build they plan to use for Safari updates?
Safari 3.1's WebKit build (525.13) has two Symphony-affecting bugs, so expect more problems with S2b5 + Safari 3.1. I haven't found any, but it would be really lucky if there weren't more, lurking.
- Race conditions between
DOMContentLoadedevent anddocument.readyStatetimer meansDOM.onreadyis called twice document.querySelectorAllerroneously returns zero matches under certain conditions
Both of these issues are fixed in later WebKit builds, but for now here's a patch to admin.js with workarounds:
-
-
- Nils
- 20 Mar 08, 5:42 pm
- Comment #5
Thanks for the fix.
Create an account or sign in to comment.
I'm not sure if it's just me: Is it possible that the debug mode does not work with Safari 3.1 (and Symphony 2 Rev 5)? It looks like the JavaScript is not applied properly ...