ansaurus

Question

How do I debug this weird IE JavaScript Problem

Answer 1

+2 A:

As you wish.

You just missed something and it's a stupid mistake.

:)

That being said, I'd try to find out which file it is that has the faulty line 216. Perhaps it's the browser.js file? Other possibilities include:

You messed up the URL and the file isn't loaded;
The function depends on the DOM to be completely loaded, but it's called before the relevant elements are created (most JS should be done after the onload event under normal circumstances).

Vilx- 2008-11-28 22:17:42

Answer 2

+2 A:

If you can use Firefox, I would highly recommend installing and enabling the Firebug addon.

Otherwise, see some of the following for tools that might help:

Mark Renouf 2008-11-28 22:31:33

Answer 3

A:

The "Object expected" error occurs when the browser's script engine was expecting to find an object, but was unable to do so. This usually occurs when you try to make a function call, but the function itself is unavailable to the script engine, presumably because you mistyped the function name when calling it.

To successfully debug this error, you must first determine the instruction at the line number reported in the error. This cannot be done by browsing through all the source files, unless you have some psychic debugging powers. It is recommended that the exception be caught inside a JavaScript debugger. If you are debugging this under MS IE, you might want to install Microsoft Script Engine which can be installed with MS Office, or the poor man's Microsoft Script Debugger. For Firefox, there are the excellent Firebug and Venkman extensions. Jonathan Boutelle's blog post on debugging JavaScript in IE seems like a must read.

Vineet Reynolds 2008-11-28 22:48:25

Answer 4

A:

check if youre using a keyword as an identifier in yoru code

http://mattsnider.com/languages/javascript/reserved-words-in-javascript/

http://bytes.com/groups/javascript/424640-error-object-expected

http://msdn.microsoft.com/en-us/library/0779sbks.aspx

Gene T 2008-11-28 22:53:15

Answer 5

+1 A:

Try running your code through JSLint.
Add alert() calls here and there to narrow down the error to a particular location.

Ates Goral 2008-11-28 23:03:12

@Ates, I love how it's 2010 and were still using 'alert()' statements to debug javascript

Chris 2010-02-13 21:05:04

Of course, one should use the Firebug console whenever possible, but `alert` still seems to be the most "portable" way.

Ates Goral 2010-02-16 17:56:10

ansaurus

tags:

views:

answers:

How do I debug this weird IE JavaScript Problem

related questions