Site with JavaScript fails to render page in IE 6 or 7 but fine with FF

[JJA]

Previously, anything IE did not like threw some sort of error like
"object expected", etc. Now all I get is "Done" on the status bar...

I am suddenly having trouble with Internet Explorer. Both IE 7 and IE
6 behave the same way - they fail to render the page at all yet do not
seem to be detecting any errors on the client side. No errors occur on
the web server either.

I've issued VIEW SOURCE on this blank IE screen and captured it to a
text file. It looks "complete" to me and I am puzzled as to why it
won't render anything.

Yet everything renders fine with Firefox 1.5.0.11 !

I've issued VIEW SOURCE on the Firefox screen and captured it to a
text file with a different name. I've compared the IE text file with
the FF text file and they are identical.

I've replicated everything on our public web server so you experts
could have a look and offer comments or ideas.

Please browse the following and compare Firefox results to IE:

http://gis.cbmiweb.com/MDWmaps/

I am really stumped and hope someone can suggest something.

[christoph.saxe]

Hmmm - I took a very quick look and I wonder if it might be a simple
code problem.
I looked at it in IE's developer toolbar and when I checked the DOM,
the body tag had no children. that's why nothings displaying, while
the head is fine, and the title displays properly. I compared the
source, and the code for the body is there... so looking above the
body, trying to find something that might screw up IE's parser, I
found two candidates:

1) your <linktag isn't formed properly. you have <link></>; it
should be <link /for XHTML.

2) you have your inline script (browser detection) inside a comment,
but you haven't closed the comment. for some reason, FF as well as
Dreamweaver ignore this, however, the first following closed comment
is inside of the body tag (<!-- header -->) - I wonder if that's it.
On Apr 10, 12:34 pm, "JJA" <johnadam...@gm ail.comwrote:

Previously, anything IE did not like threw some sort of error like
"object expected", etc. Now all I get is "Done" on the status bar...

I am suddenly having trouble with Internet Explorer. Both IE 7 and IE
6 behave the same way - they fail to render the page at all yet do not
seem to be detecting any errors on the client side. No errors occur on
the web server either.

I've issued VIEW SOURCE on this blank IE screen and captured it to a
text file. It looks "complete" to me and I am puzzled as to why it
won't render anything.

Yet everything renders fine with Firefox 1.5.0.11 !

I've issued VIEW SOURCE on the Firefox screen and captured it to a
text file with a different name. I've compared the IE text file with
the FF text file and they are identical.

I've replicated everything on our public web server so you experts
could have a look and offer comments or ideas.

Please browse the following and compare Firefox results to IE:

http://gis.cbmiweb.com/MDWmaps/

I am really stumped and hope someone can suggest something.

[JJA]

On Apr 10, 3:57 pm, "christoph.s... @gmail.com"
<christoph.s... @gmail.comwrote :

Hmmm - I took a very quick look and I wonder if it might be a simple
code problem.
I looked at it in IE's developer toolbar and when I checked the DOM,
the body tag had no children. that's why nothings displaying, while
the head is fine, and the title displays properly. I compared the
source, and the code for the body is there... so looking above the
body, trying to find something that might screw up IE's parser, I
found two candidates:

1) your <linktag isn't formed properly. you have <link></>; it
should be <link /for XHTML.

2) you have your inline script (browser detection) inside a comment,
but you haven't closed the comment. for some reason, FF as well as
Dreamweaver ignore this, however, the first following closed comment
is inside of the body tag (<!-- header -->) - I wonder if that's it.

On Apr 10, 12:34 pm, "JJA" <johnadam...@gm ail.comwrote:

Previously, anything IE did not like threw some sort of error like
"object expected", etc. Now all I get is "Done" on the status bar...

I am suddenly having trouble with Internet Explorer. Both IE 7 and IE
6 behave the same way - they fail to render the page at all yet do not
seem to be detecting any errors on the client side. No errors occur on
the web server either.

I've issued VIEW SOURCE on this blank IE screen and captured it to a
text file. It looks "complete" to me and I am puzzled as to why it
won't render anything.

Yet everything renders fine with Firefox 1.5.0.11 !

I've issued VIEW SOURCE on the Firefox screen and captured it to a
text file with a different name. I've compared the IE text file with
the FF text file and they are identical.

I've replicated everything on our public web server so you experts
could have a look and offer comments or ideas.

Please browse the following and compare Firefox results to IE:

http://gis.cbmiweb.com/MDWmaps/

I am really stumped and hope someone can suggest something.

Yes that was it .... thanks for looking. I added the closing comment.

[Randy Webb]

ch************@ gmail.com said the following on 4/10/2007 3:57 PM:

Hmmm - I took a very quick look and I wonder if it might be a simple
code problem.
I looked at it in IE's developer toolbar and when I checked the DOM,
the body tag had no children. that's why nothings displaying, while
the head is fine, and the title displays properly. I compared the
source, and the code for the body is there... so looking above the
body, trying to find something that might screw up IE's parser, I
found two candidates:

1) your <linktag isn't formed properly. you have <link></>; it
should be <link /for XHTML.

IE doesn't know what XHTML is so it is a moot point. It will all become
tag soup HTML. But why server XHTML to a browser that doesn't know what
it is?

Answer:It destroys the order of the conversation
Question: Why?
Answer: Top-Posting.
Question: Whats the most annoying thing on Usenet?

--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq/index.html
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[RobG]

On Apr 11, 6:25 am, "JJA" <johnadam...@gm ail.comwrote:
[...]

Yes that was it .... thanks for looking. I added the closing comment.

Wrong fix. HTML comment delimiters inside script elements are a
complete waste of time (as you've discovered), remove them entirely.
In an XML document, browsers have a right to ignore *anything* between
<!-- and -->, including script. But using XHTML on the web is
pointless, use HTML 4.01 strict.

<URL:
http://groups.google.com.au/group/co...ee3e381d9b2755

>

The best way to include script in an XML file is to use an external
script file. If you really must include script, use CDATA delimiters:

<script type="text/javascript">
<![CDATA[
... unescaped script content ...
]]>
</script>

<URL: http://www.w3.org/TR/xhtml1/#h-4.8 >
--
Rob