|
Also I find the hack below quite nice for debugging every once
in a while regardless of the browser: if( !confirm(debugging info) ) halt; “halt” throws a parse error only if you press cancel on the
confirmation box. From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gregory
Hill Safari has a built-in debugger that is nearly useless, and on top
of that, hidden by default. Google for safari _javascript_ console and you
should find instructions on how to enable it. It will tell you when it
has errors, but provide little to no information about what they are.
Someone else may have more info for you. Force Quit on Mac = Cmd+Option+Esc (Cmd is the apple logo key). Greg From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sam This
is way OT, but here goes... I've
had an iBook for 2 days now and am debugging a web built with prototype/script
aculo / windows / etc... I have no real experience on a Mac. Occasionally,
there's no better way to debug _javascript_ than an alert in a loop... Once I
have the information information I want from the alert, the loop may want to
execute another 300 times. I have no idea how to kill Safari like I would
do on a PC: CTRL+ALT+DEL, select the task, and stop. Any help on how to
abort Safari when it is hovering on an alert? Second,
any suggestion as to a good _javascript_ debugger for Safari? Sam |
_______________________________________________ Rails-spinoffs mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
