In article <[EMAIL PROTECTED]>, Henri Sivonen <[EMAIL PROTECTED]> wrote:
> I'm generally all for strict standards compliance and honoring the > Content-Type header. However, I'm afraid that some people are going to > use the effect of bug 46225 as an excuse to make even harder to activate > the standards mode. That would be bad. Then authors might give up with > Mozilla's standards mode and focus on Mac IE 5, Windows IE 6 and Opera 5 > & 6, which would make Mozilla appear to be to quirky browser. The whole reason I posted here is *because* Mozilla appeared to be a quirky browser. ;-) Look at it from my point of view: I was extremely careful to create a document that matched all of the W3's standards for XHTML and CSS, the documents looked beautiful in all browsers (even Mozilla, locally), then I popped it up on a server and Mozilla was the only one that broke. I followed all of the rules, and Mozilla is the only browser that slapped me for it... I won't muddy the waters by filing a bug report about issues that are over my head, but if you're trying to avoid having Mozilla look quirky, the current behavior is not working. Thanks for all of the info and help. My workaround now is to drop back to HTML 4 Transitional, which isn't the latest-and-greatest (my original goal) but works fine. Mike
