Works in firefox but doesn't load in Internet Explorer 6

[Ranjan]

Does anybody know if we could have bugs in our program such that the
compiled page would load properly in FireFox but wouldn't do so in
Internet Explorer 6.

I tried to load the compiled page without using a webserver (i.e.,
directly opening the index.html file). In which case, the firefox
doesn't complain about anything but Internet Explorer would show up
with run time error (object is null). And would open up a debugger to
debug those messy compiled javascript.

[dominik_steiner]

Hi Ranjan,

IE6 is a nightmare. The only thing you can do is to compile your GWT
code with -style DETAILED or -style PRETTY and work your way through
the javascript file to find the reason for the error.

HTH

Dominik

[oleber]

Hi

Do the correct thing.

Start removing as much as you can from your application until you
identify the error and post it. Like this the bug can be solved and
all the community will benefit.

Probably the -style DETAILED or -style PRETTY can help

Marcos

On Mar 6, 8:21 am, "dominik_steiner" <Dominik.Stei...@partner.bmw-

[Ranjan]

Hi oleber,

Thanks for the advice. I tried it out and it seemed there is some
error while parsing an XML file.

I have an asynchronous request in the program that returns an XML
file. I tried to load the XML file independently. Firefox accepted the
response as a valid XML response whereas internet explorer gave an
error:
Only one top level element is allowed in an XML document. Error
processing resource
The actual XML response is as follow:

<?xml version="1.0"?>
<Response>
<Failure>0</Failure>
<Users Count="1" Page="1" PageSize="1000">
<UserInfo>
<ID>832411C5-A9DC-4988-6C90-E8B6DC6599C2</ID>
<Name>User1</Name>
<Description>Guest User</Description>
<CreatedDate>3/13/2007 6:42:59 PM</CreatedDate>
<Online>false</Online>
<LoggedInTime>12:00:00 AM</LoggedInTime>
</UserInfo>
</Users>
</Response>

I don't see any problem in the XML. Do you have any idea?

[Ranjan]

Well finally I found out. I was implementing my own HTTP server and
responding with HTTP 1.0 version which made IE to respond in quite a
different way. I also had a small bug in the program which was easily
tackled by Firefox but IE couldn't. Besides that IE was trying to be
smart and using cache feature. I had to include "Cache-Control" in the
HTTP Response header to work around. Finally everything is going well
now.