But before I do, one last bit of geekery. I have made a discovery. Now, before I go any furthur, I have to mention that Safari has a very good rendering engine. It’s one of the few, proud browsers to pass the ACID2 test. The thing is, it’s scripting support just plain sucks. This is a statement I can back up.
I stumbled across this bug because I’ve been using the wonderful FireBug while developing some stuff. It appears Safari has it’s own console functions and the api’s are not exactly compliant. Still, I don’t think any JavaScript blunder should ever be able to just kill a browser.
Tried this with safari 3 and it did nothing.
BTW : I do read your blog