I'm still unclear on the direction we should take here. I'd like to hear
from other committers :-).
Thanks,
Dave
From: Martin Cooper [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: Re: [VOTE] How to implement XHMTL
assumptions about how the tag is working.
-Original Message-
From: David Graham [mailto:dgraham1980;hotmail.com]
Sent: Wednesday, November 13, 2002 9:51 AM
To: [EMAIL PROTECTED]
Subject: Re: [VOTE] How to implement XHMTL support
I'm still unclear on the direction we should take here
whisperDon't bother drawing a ballot up - these guys don't use it!
They're all like thinking outside the box and adding options to it,
dude! ... and there's that one fellow who is always saying put your
code where your mouth is - we only vote on code - while standing there
with a wild, Clint
-Original Message-
From: Craig R. McClanahan [mailto:craigmcc;apache.org]
The presumption of storing the outer xhtml setting
(independent of *how*
you do so) is to let the included page automatically adapt to
the outer
page's choice - presumably, that lets you use the same
]
Subject: RE: [VOTE] How to implement XHMTL support
Date: Wed, 13 Nov 2002 09:29:21 -0800
-Original Message-
From: Craig R. McClanahan [mailto:craigmcc;apache.org]
The presumption of storing the outer xhtml setting
(independent of *how*
you do so) is to let the included page
Forgot this:
5. Tags nested in html:html xhtml=false will not be rendered in xhtml
regardless of any other settings.
Dave
From: David Graham [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: [VOTE] How to implement XHMTL support
Date
-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: RE: [VOTE] How to implement XHMTL support
Date: Wed, 13 Nov 2002 10:06:56 -0800
-Original Message-
From: David Graham [mailto:dgraham1980;hotmail.com]
What if we
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
with
it.
David
From: Martin Cooper [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: RE: [VOTE] How to implement XHMTL support
Date: Wed, 13 Nov 2002 11:10:29 -0800 (PST)
On Wed, 13 Nov 2002, David Graham wrote:
What
On Wed, 13 Nov 2002, Eddie Bush wrote:
big-snip/
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
-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: RE: [VOTE] How to implement XHMTL support
Date: Wed, 13 Nov 2002 11:10:29 -0800 (PST)
On Wed, 13 Nov 2002, David Graham wrote:
What would html:isXhtml/ do?
This would be the way
Martin Cooper wrote:
On Wed, 13 Nov 2002, Eddie Bush wrote:
big-snip/
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
Neither am I. Absolutely correct naming is almost impossible, it's just
a good goal. If you can't make it perfect, the documentation should
take you the rest of the way. Make sure that the documentation for the
html and xhtml tags refer to each other. A boilerplate comment
about this in each
I'll be making over the next few days.
David
From: Hajratwala, Nayan (N.) [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: 'Struts Developers List' [EMAIL PROTECTED]
Subject: RE: [VOTE] How to implement XHMTL support
Date: Wed, 13 Nov 2002 15:18:57 -0500
I think
Hi,
A Dimecres 13 Novembre 2002 20:45, Martin Cooper va escriure:
On Wed, 13 Nov 2002, Eddie Bush wrote:
big-snip/
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
library tags to render in xhtml.
If you want to reuse a jsp in an html project then don't code it with xhtml
tags.
David
From: Antoni Reus [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: Re: [VOTE] How to implement
a non-struts jsp page,.. oh well, I think now I
completely agree with the above :-)
Salut!
-- Antoni Reus
From: Antoni Reus [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: Re: [VOTE] How to implement XHMTL
Just so I understand, you're experimenting with making tags generated
from a jsp:include be xhtml-compliant even if the original page wasn't
specified as being xhtml-compliant? It seems to me that XHTML
compliance is an attribute of an html element and its nested elements
(including the
Yes, I have already implemented choice 1. Good points David.
Dave
From: Karr, David [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: RE: [VOTE] How to implement XHMTL support
Date: Tue, 12 Nov 2002 16:14:10 -0800
We need to ensure that HTML taglib tags in included JSP pages also heed
the xhtml attribute. That isn't the case with what's there now, because
findAncestorWithClass() will fail for the tags in the included pages.
Note that this is why the form tag stores itself in a request attribute.
20 matches
Mail list logo
