Martin Cooper wrote:
On Wed, 13 Nov 2002, David Graham wrote:What would <html:isXhtml/> do?
This would be the way Craig was seeking for an included page to tell its own Struts tags whether to render XHTML or plain HTML. It would set a *page* context attribute, which the subsequent tags on that page would check. As a corollary, the <html:html xhtml="true"> tag should set the key in *page* scope rather than request scope, so that each page has to make its own decision.If we're going to use a tag I think it should be like this:
<html:xhtml>
<html:form>
<html:text/>
</html:form>
</html:xhtml>
Do you mean a separate tag from the <html:html> tag, instead of using <html:html xhtml="true">, or are you referring to another tag for the XHTML-ness ;-) of the content? If the former, I'm not sure why we would want that. If the latter, I disagree that it should be a body tag, since it needs to be an all-or-nothing tag, not one that applies only to its body.
I too am confused as to why we would need an additional tag.
If the outermost document is meant to enforce XHTML, how can an included piece *not* conform to XHTML and the entire document still be XHTML? I ... feel like we're attempting to over-design - but maybe I'm just showing my own ignorance (which is something I don't think I'll ever learn not to do - I learn way too much from being willing to do it).Any tag inside <html:xhtml> would be rendered as xhtml. This tag would only
be useful for jsp included files.
Another question: what if <html:xhtml> is nested inside
<html:html xhtml="false">?
I think we should probably log a warning. In many cases, the resulting output will work, but we need to flag that there's a potential problem. -- Martin CooperDavid
--
Eddie Bush
--
To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
