> <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." If there's a bump on every five roads in a nation of cities, you don't tell the cities to replace the road system, you design a car with better shocks. I'm an end user. I shouldn't have to care about MIME types being wrong server-side for terribly obvious files. (dmg, sit, hqx, gzip, tar, exe, jpg, gif, and png, for examples.) If Safari works in this respect (I hate to compare, but everyone I know does), Camino should, too. Two cents. Take 'em as-is. :-) -/- Mikey-San "Johnny Lemonhead! I haven't seen you around here since we dropped your insulin supply into the woodchipper." _______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino
