<snip>
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
I get the "standards-compliant" thing. Standards are good. Yay standards.
. . . But who in the world wants a million pages of text for "http://site.com/files/hotfile.dmg";?
Standards are one thing; logic is another. You can't fix the thousands of misconfigured servers out there, but you certainly can tell a browser, "Okay, these twelve extensions, well, there's no reason to display them as text. The server's telling you it's text, but trust me, .sit is not text."
Hmm . . . let me toss an idea into the ring:
*nix-Webservers (e.g. Apache) use magic-files to determine the filetype.
So does OS X.
So why not use the OS X magic-file to do a little content-sniffing in files sent as text/plain?
If the system used can handle it, it will be in the magic-library. If not - display as text.
But: this should *only* be true for binary and stuff like that. If a webmaster is too lazy to configure the output of ASP right or sends HTML as text/plain my mistake, The browser should display it as text! (I agree with Marcello at this point, then)
Greetings . . . Martin
--
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
