Perl knows nothing about browsers. And browsers know nothing about Perl.

Browsers simply interpret the HTML and/or Javascript that your Perl program creates. If the HTML or Javascript doesn't work in every browser then you will have a problem.

The solution is to look at your HTML and Javascript and work out how to achieve the effects you want in a cross-browser manner (sticking to W3C standards would be a good start). You then write a Perl program that creates that HTML and Javascript.

Well, Internet Explorer might know something about Perl ;)

(This has nothing at all to do with CGI though and doesn't have any bearing on the OP's question.)

Check your JavaScript for errors. W3C validator doesn't check errors in your JavaScript code. It's validate only markup (HTML+CSS).

Perl knows nothing about browsers. And browsers know nothing about Perl.

While this is true, it misses the point. Code written in Perl can most definitely know something about browsers.

While I very much doubt it has anything to do with the OP's question, CGI.pm does in fact check the user agent to work around a bug in IE3.01 on macs.

-sauoq
"My two cents aren't worth a dime.";

But don't forget that browsers, specially MSIE's, don't fit W3C recommendations/specifications fully.

I validated using the above link.

Its fine.

"Passed validation"

Here's what's wrong then :) IE is notoriously known for disrespecting standards. Unfortunately, like many others, you'll have to "code for IE". Sometimes both coding for standards and IE is close to impossible, unfortunately.

Can CSS be a problem ?

One solution is to use onLoad or even better DOM.Ready from JSAN.

;)Although, in practice, in the corporate Windows environment I would be also tempted to let the problem happen and cry non-responsibility for Microsoft problems ... "I can't help it if the corporate standard is to choose a browser that has faults I can't support ;)"

Your first step (with respect to the reply by moron) is to announce that you have achieved success and completion with the project using the Firefox browser. All those who wish to use this new interface should use this browser until further coding (and additional funding) can be implemented to accommodate non-compliant browsers. Then it's time to start hacking as davorg and the others have suggested.

Using CSS may also bring rise to problems in the future using IE. MS seems to have some version problems with that, even though they have work-arounds, it will become an ongoing task to maintain the compliance of CSS and IE browsers.

I am in corporate world so I can't ignore IE . :-)

So am I, and I can. That's partly because we don't try to do anything fancy, but also because our HTML is written to comply with standards, and IE's compatibility these days is a *lot* better than it used to be. People who tell you that IE blithely ignores standards are, to a certain extent, FUDding.