Instead of a "disableElement" parameter, you could disable it for <span> elements unless they have the "element" parameter set.
On Wed, 20 Sep 2006 18:24:11 +0200, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > I like this idea. I guess that would mean we'd still have to offer some > flexibility by having a "disableElement" or similar parameter that means > "don't output the element tag at all" ? > > I haven't needed to add it yet but I predict that I'm going to need to > finally add in the ability to insert / remove content into different > portions of the page for some things. > > Of course, leaving a fieldset div visible may have unpredictable UI results > if people are using css styling rules on them..I could always "detect" if > something is involved in a potential ajax update and still render it with a > style display of "display:none" but this starts to feel a little too heavy > handed. > > On 9/20/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: >> >> Components which have an "element" parameter (If, For, etc.). >> >> Perhaps we should code it as: >> >> if the component's tag is "span", honor the element parameter, >> else honor the component's actual tag >> >> So: >> >> <fieldset jwcid="[EMAIL PROTECTED]" element="fieldset" >> condition="ognl:book.name"> >> >> could be replaced with >> >> <fieldset jwcid="[EMAIL PROTECTED]" condition="ognl:book.name"> >> >> To the same result. >> >> -- >> Howard M. Lewis Ship >> TWD Consulting, Inc. >> Independent J2EE / Open-Source Java Consultant >> Creator and PMC Chair, Apache Tapestry >> Creator, Apache HiveMind >> >> Professional Tapestry training, mentoring, support >> and project work. http://howardlewisship.com >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
