<snip>Well, OK. I mean, technically, that's correct. Uhm... but, right, we know that in the real world things aren't always exactly to spec, like "http://bla.com/bla"; gets mapped to "http://bla.com/bla/"; (server fails the first time, then inserts the trailing slash) -- so, could there be some (hidden? in the user.js file or whatetever) pref to have Camino basically treat all text as HTML? Or at least, before concluding that it's *not* to be rendered, to do one more check and see if the content begins with "<html>"?
I see the problem also when I use Mozilla 1.5, so this is *not* a Camino-specific problem.
The reason of this behaviour is that the underlying rendering engine, Gecko, is the most standard-compliant engine in the world. And this behaviour is also standard-compliant.
Please note that I say this *not* as a mozilla coder, but as a user and webdesigner. I really enjoy the Gecko engine and hate the others because I have to introduce tons of quirks in my webpages so that on the one hand my page stays standard-compliant and on the other Safari and IE render it right.
Therefore I have no mercy for webdesigners and webmasters who are too lazy to code and configure right.
Greetings . . . Martin Creutziger
--
Never ask a man what computer he uses. If it's a Mac, he'll tell you. If it's not, why embarrass him?
- Tom Clancy, Novelist
_______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino
