Compatible Browser With Css My page was tottaly messed-up

[osiris1405241478 0]

I built a page using Dreamweaver MX, and CSS in separate page then link it to index.php, it runs smoothly using MSIE.But the disaster come out when I use Mozilla (Linux SuSE), all layout in page was tottaly different ..........(but runs better using Opera)All layer (DIV) become upside-down, I was frustated looking for the "error" by modifying the (DIV) scripts. Is it compatibility problems I got here ??Anyone can help ???Rgds,Osiris

[foolakadugie 0]

  I built a page using Dreamweaver MX, and CSS in separate page then link it to index.php, it runs smoothly using MSIE.

But the disaster come out when I use Mozilla (Linux SuSE), all layout in page was tottaly different ..........(but runs better using Opera)

All layer (DIV) become upside-down, I was frustated looking for the "error" by modifying the (DIV) scripts.

Is it compatibility problems I got here ??

Anyone can help ???

 

Rgds,

Osiris

1064329185[/snapback]

It might help if you provide us with a link to the site or at least the source code so we can see what is going on.

[Hercco 0]

We definitely need the sources... But few things:

Have you run your code through a validator? If not do it and along with the source code paste the results here. The W3C CSS validator is availble here: http://jigsaw.w3.org/css-validator/ and HTML validators here: http://validator.w3.org/

Generally speaking it is not a good idea to test your work-in-progress code with MSIE. IE respects the standards rather poorly and the results with proper browsers can be dramatically different. Instead do your developing and testing with a Gecko based browser or with Opera and make sure its standard comliant. It probably won't look like intended on IE, but results are still readable.

[twitch 0]

The problem with Internet Explorer, like most Microsoft Products, is that it seems to guess what is meant to be shown. That means that the worse web-designers/developers can make a back-end crap site and it still look good on the front-end. Whereas the decent browsers like Mozilla Firefox, do exactly what it says on the tin (or source code as it may be). This, is why standards were set, to ensure the better browsers were maintained for.Anyway, onto the problem.I think the problem you have run into is the box-model. IE and a few other browsers including Opera have difficulties in displaying this model properly, whereas Mozilla does not. Although this may sound totally wrong - it isn't if you think about it logically. Linking back to what I said in the beginning of this post, IE and a few others 'guess' what it should look like, therefore when developers preview their sites in IE, they see that it looks right and don't bother with the others. Now, this is where the real problem lies. Mozilla shows things as they are formatted, so if it is formatted wrongly, it will show it exactly how it is. And this is the way browsers should behave, to enforce usability and compatibility on developers, an accompanying push with XHTML/XML. Anyway, your problem is the box-model system. It has been developed inaccurately, and without the source-code (as pointed out in other posts) there is nothing we can do about it.

[osiris1405241478 0]

The problem with Internet Explorer, like most Microsoft Products, is that it seems to guess what is meant to be shown. That means that the worse web-designers/developers can make a back-end crap site and it still look good on the front-end. Whereas the decent browsers like Mozilla Firefox, do exactly what it says on the tin (or source code as it may be). This, is why standards were set, to ensure the better browsers were maintained for.

 

Anyway, onto the problem.

 

I think the problem you have run into is the box-model. IE and a few other browsers including Opera have difficulties in displaying this model properly, whereas Mozilla does not. Although this may sound totally wrong - it isn't if you think about it logically. Linking back to what I said in the beginning of this post, IE and a few others 'guess' what it should look like, therefore when developers preview their sites in IE, they see that it looks right and don't bother with the others. Now, this is where the real problem lies. Mozilla shows things as they are formatted, so if it is formatted wrongly, it will show it exactly how it is. And this is the way browsers should behave, to enforce usability and compatibility on developers, an accompanying push with XHTML/XML.

 

Anyway, your problem is the box-model system. It has been developed inaccurately, and without the source-code (as pointed out in other posts) there is nothing we can do about it.

1064329384[/snapback]

Thanx for these information.

I think the main problem is, Mozilla display the format as is, because I've been use MSIE for testing the script , so when I tried to display through Mozilla, boom !

 

Anyway, now I use Mozilla for testing.

 

Thanx guys ...

 

Best Regards,

Osiris

 

>> Check this up pestokil.com (but I haven't change the script, so maybe not suitable for perfect eyes using mozilla).