|
|
Posted by Jukka K. Korpela on 03/23/07 11:34
Scripsit Ioannis:
> I have one page which for some reason misbehaves on my IE
> (6.0.2800xpsp2.050301) and displays two errors which I have no idea
> what they are:
In any case, they are error messages about JavaScript constructs. IE doesn't
bother telling the user anything about HTML or CSS errors. You can also make
it suppress JavaScript error messages; many people do that, either knowing
what they are doing or not knowing that.
> http://ioannis.virtualcomposer2000.com/spectroscope/phasmaplan.html
>
> Clicking on the error icon after the page loads, IE reports two
> errors:
>
> Line: 3
Did you check what actually appears on line 3? (View Source) You might get
something different from what others get, for various reasons (e.g.,
decisions by the server, or filtering somewhere). Or this might refer to a
line in an external file, who knows.
> Line: 271
This seems to refer to a <script> element after </html>. It's syntactically
invalid, and you should expect nothing specific except differences between
browsers and odd behavior.
> Is there a possibility the server alters the page somehow?
Of course. It's the server that sends it.
> I can see that it adds some stuff to the end,
Well, that means altering, doesn't it? And making it invalid.
> I am using deprecated html on all my pages, but IE complains only on
> this one.
So what? Web pages often have scripting errors, which may or may not mean
anything. But you can _know_ that the element after </html> is an error. Fix
it if you can. This may mean that you need to give up using "free" web
space. TANSTAAFL!
(The server-side code that the script element invokes may perform some
checking and do different things according to the "calling" page. This is
just a potential explanation that might make you feel more comfortable.
:-) )
--
Jukka K. Korpela ("Yucca")
http://www.cs.tut.fi/~jkorpela/
Navigation:
[Reply to this message]
|