Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #8716

Re: Diagnosing JS error that is not reported

Show all headers | View raw

In comp.lang.javascript message <aaf4dcf8-e665-4b88-807d-f6e6d0292fae@v5
g2000yqn.googlegroups.com>, Mon, 28 Nov 2011 12:07:33, DrKen
<javajedi2@yahoo.com> posted:

>  I am having trouble finding the error in my .js file.  I have a web
>page that I am using outside of its web application in order to test a
>small change to a JavaScript file.  I am getting an error while the
>page is rendering.  It stops part way through rendering. My experience
>has been that this is a JavaScript error.  However, when I try to open
>the .html file in Firefox, the Error Console seems to list no errors,
>warnings, or messages for the page.  I opened Firebug on the page and
>then opened the .html file and the Firebug part disappeared.  I tried
>using jslint but that gave me all sorts of grief over code that has
>worked for three years and stopped aorund line 30 instead of giving
>errors for the entire file . Is there a good tool to find JavaScript
>coding errors?  Thanks.

Then there is obviously at least one actual error in your HTML or
JavaScript files.  More detail cannot be given without seeing those
files.

One possible explanation is that you have a bad loop statement trying to
execute an infinite (approximately) number of times, and that your
browser has not got an enabled loop detector.

Another is that your browser's error detector is nor detecting, perhaps
being set to show only messages,  Verify that by introducing a known
error.

A simple test is to introduce an alert(number) call at a place that you
know execution reaches (to prove you can do it), and others where it
might or might not be reaching.  But be careful not to do that in high-
count inner loops.

Another test is to disable JavaScript and see whether the whole of the
HTML renders as then expected.  If it does not, you have at least one
non-JavaScript error.

You should, of course, have validated the HTML & CSS at www.w3.org, and
have said so.

-- 
 (c) John Stockton, nr London UK  ?@merlyn.demon.co.uk  IE8 FF8 Op11 Sf5 Cr15
   news:comp.lang.javascript FAQ <http://www.jibbering.com/faq/index.html>.
   <http://www.merlyn.demon.co.uk/js-index.htm> jscr maths, dates, sources.
   <http://www.merlyn.demon.co.uk/> TP/BP/Delphi/jscr/&c, FAQ items, links.

Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Diagnosing JS error that is not reported DrKen <javajedi2@yahoo.com> - 2011-11-28 12:07 -0800
  Re: Diagnosing JS error that is not reported Denis McMahon <denismfmcmahon@gmail.com> - 2011-11-28 21:37 +0000
    Re: Diagnosing JS error that is not reported John G Harris <john@nospam.demon.co.uk> - 2011-11-29 15:45 +0000
      Re: Diagnosing JS error that is not reported Denis McMahon <denismfmcmahon@gmail.com> - 2011-11-29 18:07 +0000
        Re: Diagnosing JS error that is not reported John G Harris <john@nospam.demon.co.uk> - 2011-11-30 16:49 +0000
  Re: Diagnosing JS error that is not reported Gene Wirchenko <genew@ocis.net> - 2011-11-28 14:07 -0800
  Re: Diagnosing JS error that is not reported Dr J R Stockton <reply1148@merlyn.demon.co.uk> - 2011-11-29 19:38 +0000
    Re: Diagnosing JS error that is not reported Tim Streater <timstreater@greenbee.net> - 2011-11-29 23:57 +0000
  Re: Diagnosing JS error that is not reported "J.R." <groups_jr-1@yahoo.com.br> - 2011-11-29 22:31 -0200

csiph-web