1

I have a big (probably) javascript problem.

i have a long and complex script on the page based on mootools framework, in FF and other browser everything works fine, but in ie 6 and 7 i got "error:153 (sometimes 84) Unspecified error" and the strange thing is in IE8 that show me the error "Object doesn't support this property or method".

someone know the possible cause of the problem? o maybe someone know a list of IE's unsupported property or method?

1
  • if in doubt, resorting to alerts to pinpoint the problem is not unreasonable at all Commented Jun 12, 2009 at 9:19

5 Answers 5

2

In IE8 you can get the line number of the error, then right-click -> view source. IE8 has a proper source, which includes script lines, so you should quickly be able to find the source of your error.

Sign up to request clarification or add additional context in comments.

1 Comment

yes that's right. But i have minimized js, i will try to use unminimized version.
2

If the script you're using isn't obfuscated or all on one line, you could use the JavaScript debugger in IE8 to pinpoint the object which is causing the error. Press F12 to open the Developer Tools, go to the Script tab, and click the "Start Debugging" option. If there's an error it may well break on the relevant line. If not you can set some breakpoints and step through the code.

Comments

1

You can also use IE8 developer tools http://blogs.msdn.com/ie/archive/2008/09/03/developer-tools-in-internet-explorer-8-beta-2.aspx to debug.

For other version I suggest you use Web developer tool bar which is similar to web developer tool bar for firefox.

1 Comment

thanks much, i'll try the developer tools, i hope it will help me
0

Its near impossible to tell what the problem is with this information (at least for me).

For IE6/7 I suggest adding a few alerts to the javascript in intervals to find out exactly what line of code is causing your problem. If you know which object is causing the error, it is usually quite simple to find out what the exact problem is.

IE8 provides nice debugging tools, so that is a good place to start.

Comments

0

In my case the error was due to a $ mapping conflict.

Using jQuery instead of $ solved the issue.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.