Log in

View Full Version : how to remove this error


kaali
07-23-2006, 02:49 PM
Hello!

in my html page this error shows up:

http://www.filecabin.com/up1/1153666111-untitled.jpg

its strange because on line 2 there is only tag of <head>
Twey
07-23-2006, 03:04 PM
We'll need a link to your page.

And I see a backslash in that URL. There should never be a backslash in an URL.
jscheuer1
07-23-2006, 04:46 PM
The problem with IE's javascript error reporting as well as with many others is that they often report line numbers erroneously due to script instructions being executed as a part of an onclick event, a setTimeout() method and other things. IE's is particularly bad because, if a script is external, it will often report the line number on the external file but state the location as the html page that the script is being used on. Most other error reports do not have this additional handicap.

The invalid character error often but not always can refer to the use of entities where the actual character is what is intended. These kinds of errors can just 'creep in' to code pasted to source improperly using a WYSIWYG editor such as FP or DW. One example of this would be having:


if(a&amp;&amp;b)

where:


if(a&&b)

is intended.


And I see a backslash in that URL. There should never be a backslash in an URL

Usually that is correct but, if IE is being run locally on a page on the user's computer and that page was loaded directly into the browser for testing purposes, that type of slash appearing in the error report can be innocent enough.
Twey
07-23-2006, 04:51 PM
if IE is being run locally on a page on the user's computer and that page was loaded directly into the browser for testing purposes, that type of slash appearing in the error report can be innocent enough.And there would be no need to blank out the URL. :)
jscheuer1
07-23-2006, 04:59 PM
Originally Posted by jscheuer1
if IE is being run locally on a page on the user's computer and that page was loaded directly into the browser for testing purposes, that type of slash appearing in the error report can be innocent enough.

And there would be no need to blank out the URL. :)

That's not necessarily true - some folks might not want the directory structure of their HD revealed in any public fashion. But, it did occur to me just after my initial detailed response to the original question in this thread that I should have included the fact that yes, if the information I provided there is not enough to solve the problem, we would indeed need a link to a live version of the page (or the full code involved) to be of any specific help.