pf » JavaScript Debugging with Safari

February 17, 2005

JavaScript Debugging with Safari

If your doing web development or testing on Safari, JavaScript exceptions are quiet, like they are on most modern browsers (remember the days of annoying javascript error popups?). After looking around in the menus, or trying to type javascript: in the location bar (this brings up the javascript console in mozilla) you will soon find that there is no way to see your JavaScript exceptions by default.

Safari does in-fact have some handy debugging tools for web developers (DOM Tree, User Agent Spoofing, etc), but they are all hidden and disabled by default. The easiest way to turn on the debugging menu in safari is by installing Safari Enhancer.

Safari Enhancer Screen Shot

Make sure you check the box Debugging Menu, you can see that there are also some other handy features in Safari Enhancer. Click Apply Lasting Setting when your done.

Safari should reload and you will have a new menu called Debug

Screen Shot of Safari Debug Menu

Check Log JavaScript Exceptions in the debug menu. Now javascript exceptions will show up in your Console log (Applications / Utilities / Console).

Permalink | Add Comment |

add to del.icio.us

7 people found this page useful, what do you think?

Trackbacks

Trackback Address: 230/AC55A652915DE15CEF0427C9B31CC06E

Comments

On 02/22/2005 at 9:47:34 PM MST Bertrand Le Roy wrote:

Well, if you call things like ":TypeError - Undefined value" a useful error message... No line number, no source code, nothing useful really.

On 03/07/2005 at 11:29:58 AM MST jay wrote:

how about this:

(event handler):Undefined value

yeah, that's greatly helpful. Thanks Apple!

On 03/25/2005 at 1:33:51 PM MST scott wrote:

It seems like the Page Load Test and "Sample" files that Safari generates might be handy, but I can't find any information on how to use either of these capabilities that appear in the Debug menu.

Does anyone have any information on how these features work?

On 03/08/2006 at 9:55:38 PM MST Rich wrote:

I get "SyntaxError - Parse error Line 1". Really useful. </sarcasm>

Considering that Safari's scripting support is pretty-much as non-standard as any other browser, they should really include decent debugging tools if they expect anyone to support their platform.

On 09/11/2006 at 9:15:44 AM MDT Jonathan wrote:

I actually enabled the debug menu via the Terminal. My JavaScript console displays error with the line number visible and when you double-click on the error it will launch the js file in source view and hightlight the line that is giving the error.

On 04/22/2007 at 4:57:28 PM MDT Charlie wrote: