Timothy Stone wrote: > I think that Stripes is producing a response that makes a terrible > assumption: the Web Tier/View developer is writing to the XHTML 1.0 > Transistional DTD.
I agree. I don't want to use XHTML, yet if I use Stripes it produces invalid HTML - albeit not so broken that browsers can't render it. > And while I think that there are many that are, including leaders of > Stripes, I might suggest that they are doing it wrong. Especially if > they are not mime typing the response correctly. And if they are not > using the correct mime type, then they are not writing XHTML, but > invalid HTML. Absolutely so. On a correctly-configured webserver using the correct MIME type, invalid XHTML won't render at all. Virtually all the 'XHTML' pages I've seen are actually invalid, and the only reason they display at all is because they are being served as the HTML MIME type, resulting in 'tag soup'. Save the page locally, rename to .xml and open in your browser and they won't display, you'll get XML validation errors. > I also think they would be especially surprised by the experience that > their IE6/7 audience get if they were to correctly type the response. Indeed, if the content was served with the correct MIME type, IE would offer to download it and not display it. IE doesn't display XML. Period. We've discussed this in the past on this list: http://www.mail-archive.com/[email protected]/msg00032.html -- Alan Burlison -- ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Stripes-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-development
