You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Adriano dos Santos Fernandes <ad...@gmail.com> on 2011/07/01 14:13:20 UTC
Enclosures and EnclosureContainer related warning
Hi!
Sometime in 1.4, wicket:enclosure got some diagnostics warnings about
FormComponents and EnclosureContainer was added.
AFAIK, wicket:enclosure has two usages:
---------------
1) Hide some content based on its own child components, i.e.:
<wicket:enclosure child="x">
<div>
........
<input wicket:id="x" />
</div>
</wicket:enclosure>
2) Hide content based on non-child components, i.e.:
<wicket:enclosure child="x">
........
</wicket:enclosure>
<input wicket:id="x" />
---------------
My question is: isn't it safe to relax the warning for the case (1),
when the only FormComponent child is equal to the "wicket:enclosure
child" attribute?
Adriano
Re: Enclosures and EnclosureContainer related warning
Posted by Igor Vaynberg <ig...@gmail.com>.
yeah, i was going to do just that a couple of days ago and forgot.
please add a jira.
-igor
On Fri, Jul 1, 2011 at 5:13 AM, Adriano dos Santos Fernandes
<ad...@gmail.com> wrote:
> Hi!
>
> Sometime in 1.4, wicket:enclosure got some diagnostics warnings about
> FormComponents and EnclosureContainer was added.
>
> AFAIK, wicket:enclosure has two usages:
>
> ---------------
> 1) Hide some content based on its own child components, i.e.:
>
> <wicket:enclosure child="x">
> <div>
> ........
> <input wicket:id="x" />
> </div>
> </wicket:enclosure>
>
> 2) Hide content based on non-child components, i.e.:
>
> <wicket:enclosure child="x">
> ........
> </wicket:enclosure>
> <input wicket:id="x" />
> ---------------
>
> My question is: isn't it safe to relax the warning for the case (1), when
> the only FormComponent child is equal to the "wicket:enclosure child"
> attribute?
>
>
> Adriano
>
>