0

I am working on a JavaScript file and using the alert() method to print some object information. I am testing my ".js" file on Eclipse. Every now and then this information is to big to fit in the alert box so I see the alert box but am unable to see the OK button (located usually in the end of the alert box). So I end up force quitting Eclipse. The same thing also happens with some browsers (Google Chrome). Is there any way to prevent force quitting or is this somehow preventable?

I know this question is somewhat general but it happened to me a lot recently and I am wondering if this can be avoided.

M.C.
  • 1,765
  • 3
  • 29
  • 31
  • 2
    I suggest using [`console.log`](http://stackoverflow.com/questions/4539253/what-is-console-log) for debugging, theres [Firebug](http://getfirebug.com/) for Firefox and Chrome already comes with Developer tools. Avoid this whole problem with Eclipse altogether, debug within your browser at runtime. – Amy Apr 27 '13 at 16:29
  • 1
    Reference for [Console Object](http://blogs.msdn.com/b/cdndevs/archive/2012/01/03/10168757.aspx). Keep in mind that there are differences between console object for each Developer Tools. New versions of Firefox doesn't needed the Firebug extension, there's a built-in Web Console. IE and Opera also have a console. – Gustavo Carvalho Apr 27 '13 at 18:21
  • @sweetamylase I am working with console.log now. I did not know it before. – M.C. May 01 '13 at 17:05
  • @gfcarv Thank you for pointing that Firefox does not need the Firebug extension, because Firebug slows my browser. – M.C. May 01 '13 at 17:06

0 Answers0