Yeah I was afraid of that...Perhaps we should use the same behavior for span
AND div, possibly making a note that div will be rendered in 4.2.

On 9/20/06, Paul Ferraro <[EMAIL PROTECTED]> wrote:

I often use <div> tags for these types of components, because <span> is
not always contextually valid.
The logic you're proposing would cause these extra <div>s to appear in
my html.

Paul

On Wed, 20 Sep 2006 08:10:56 -0700, "Howard Lewis Ship"
<[EMAIL PROTECTED]> said:
> 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
--
  Paul Ferraro
  [EMAIL PROTECTED]

--
http://www.fastmail.fm - Accessible with your email software
                          or over the web


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

Reply via email to