> -----Original Message----- > From: Wim Fournier [mailto:[EMAIL PROTECTED]] > Sent: donderdag 17 januari 2002 15:34 > To: Struts Users Mailing List > Subject: Re: bug -> form taglib > > > > > s would really decrease render time as, when rendered as > > > xhtml, the browser looks for a closing tag and cant find it > > > > Hmm, maybe. But Struts is for rendering html, and I'm > pretty sure xhtml > > and html aren't entirely compatible... (how does your IE3.0 react on > > "<br/>" ?) > > > > > have a read at: http://www.w3.org/TR/xhtml1/#guidelines > It talks about being compatible with older versions of html
Jep, I've just seen this. > Also, why would struts want to be compatible only with html > when we are in the > process of migrating to a new standard (talking abt xhtml now)??? "migrating to a new standard" ? xhtml is a "reformulation" of html, not a replacement... Maybe I got this whole xhtml concept wrong, but I know for sure that Cocoon takes xhtml, and the very last step before sending everything to the browser is converting it to html. This would have a reason, I would think. > I think projects like struts should at least have support for xhtml. > It currently does only supply xml:lang in <html>.. but that > cant be called 'compliance' or even 'support' > > xhtml is very like html (4.0) but with compliancy towards > xml.. so by only adding > those ' />' to every opening tag and by taking a glance at > validator.w3.org > now and then, struts could support xhtml. Start sending in patches, as long as everything stays backward compatible (including older browsers), you shouldn't have too much trouble getting them in IMHO. tomK -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
