It's a nasty bug to track down; you make good html and css, it doesn't work. You look it up, and it says that the browser does it correctly. You tweak it randomly for 4 hours, then you think of the doctype...
I've done this before ;-)
Another nasty one is that Moz will not eat a .css file if the mimetype that it came through under isn't right. So, if CSS isn't in your mimetypes in your python (which it's not in 2.1) Mozilla will not use any stylesheets at all. That was another doozy to track down.
My suggestion would be to have 3 or 4 good doctype strings, and just comment all but one out. That way a novice user could just switch them without having to understand...
Stuart Donaldson wrote:
Given the comment in the writeDocType method, is it possible that the fix of removing a default DocType should be re-considered? What does it mean that some versions of Mozilla acted strangely? Mozilla has been under active development and made significant progress in bug-shooting. Perhaps the problem was with Mozilla, and we should replace the DocType?
Although as I think about it more, I am not sure that Page.py should be defining what the DocType is of the HTML the servlet will be writing.
Perhaps just an explicit note in the release notes that there is no longer a default doctype written...
-Stuart-
------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
