This is only an opinion, since we're on the topic again:
It's not so much about having different browsers. They should all interpret the same code or mark up in a predictable manor. It doesn't need to be exactly the same, it does need to be predicatable. A browser that chooses to support something, and not support something else should still provide functionality that renders or deals with the output according to the specs outlined in the whitepappers.
A browser can choose to display anything any way it wants, and that's fine. But it shouldn't even attempt to handle any code that's it's not 100% capable of dealing with. But if it is 100% capable of handling some given mark up with any crashing, choking or bad output, then it can turn all my green CSS styles into purple spotted elephant fonts for all I care. It should just let the user know that it's maybe not showing what the author intended.
Anything else simply is not standards compliant. If a browser can't deal with completely with the full spec of a particular standard, say CSS Level 1, then it should not claim or even try to. It should ignor all CSS and just render plain ol HTML. Same goes for JavaScript (which incidentally is named after a language it has nothing in common with, and is not in itself reliable, compatible or uniform).
The idea with HTML was always that if the rendering engine sees code it doesn't recoginize it shouldn't do anything with it.
In my opinion there isn't a good browser out there.
Henning Sittler
www.inscriber.com
I personally wished there was only one browser, because programming for
a common level, takes time and you loose functionality and integration.
Just my thoughts
Ben Johansen - http://www.pcforge.com
Authorized Witango Reseller http://www.pcforge.com/WitangoGoodies.htm
Latest downloads & List Archives @ http://www.witango.ws
