Wai_Wai wrote:I would really like to know why all these happen?
It's a complex problem. Every maker of a modern browser understands that the IE way of doing things is the de facto standard and tries to emulate it as best they can. Not everything IE does however can or even should be emulated: ActiveX comes to mind. The web of things that can't in practice be emulated is greatly expanded and fixed by the large body of extant websites, many of them containing code from -- ahem -- 1998, that make unfortunate assumptions about one set of functionality from others.
The choices a browser maker faces aren't clear. For example Mozilla and Opera took different paths to IE compatibility in one area used very frequently in many websites (document.all). Because of this one choice, each browser works on some sites and doesn't on others, but different sites for each. It's a backwards compatibility nightmare, and the world wide web is immovable as a planet. (In recent builds Mozilla has by the way moved closer to Opera's interpretation.)
In the end, there are incompatibilities between browsers, and it's up to website authors to deal with them. Or not.
http://hk.geocities.com/wai_wai_sir/htm ... out_go.htm is a fairly simple example that does nothing egregiously wrong. It just needs to understand that the world of browsers has changed a great deal in the last six years. Or not. After all it works fine in Firefox; it's just missing some extra flash.
Wai_Wai wrote:And how to rewrite the codes to solve the problems?
I see two, maybe three, small problem areas that need to be rewritten. The biggest impediment to most authors is that seemingly
all the popular websites offering pre-packaged sample code were written in 1998, and have never been updated. You just have to know what you're doing, and it helps if you have access to different browsers on half a dozen different machines. What a mess, eh?
Wai_Wai wrote:Does this work in Mozilla too?
I believe Mozilla plans to copy Firefox's document.all compatibility change to the Mozilla 1.7.x effort, but hasn't yet. Note that only from Mozilla 1.7 it could be picked up by some future Netscape build.
Wai-Wai wrote:Does the [character encoding] difference result from different requirements / structures / code formats firefox and IE have?
Outside my area of expertise, here. Anyone else know?
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040912 Firefox/0.10