2. For foo="prop:x" the value
> will be null if getX() is null
>
> So it's best not to use ${x} for attribute values.
>
>
>
> -- View this message in context:
> http://tapestry.1045711.n5.nabble.com/Conditional-rendering-of-HTML-attribute-tp5719323p57
ribute values.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Conditional-rendering-of-HTML-attribute-tp5719323p5719330.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscrib
On Tue, 15 Jan 2013 12:54:13 -0200, Arno Haase
wrote:
Hi,
Hi!
So - any ideas or suggestions?
Write a mixin that writes or not the attribute depending on a mixin
parameter.
--
Thiago H. de Paula Figueiredo
-
To unsu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
the following example is extremely simplified, but the underlying
problem is real.
I have a custom component with an optional parameter 'x'. If the
parameter is present, I want to render
Hello
otherwise I want the same thing but without the HTM
