I tried to fix the 5214 yesterday and it might break to many things. I guess the problem is misunderstanding of the good use to make for Enclosure. May be we can change the log level indicating an unrendered component with a transparent parent in result of the call to org.apache.wicket.Page#hasInvisibleTransparentChild() .
Ideally we should write a log trace in warning if the detected parent is an Enclosure and keep debug in other cases. __ Cedric Gatay (@Cedric_Gatay <http://twitter.com/Cedric_Gatay>) http://code-troopers.com | http://www.bloggure.info | http://cedric.gatay.fr On Tue, Jun 18, 2013 at 8:19 AM, Guillaume Smet <guillaume.s...@gmail.com>wrote: > On Tue, Jun 18, 2013 at 7:55 AM, Igor Vaynberg <igor.vaynb...@gmail.com> > wrote: > > some uis are prone to having a lot of these. eg when you hide a form > > component you also want to hide some static help markup. without > > enclosures this means having an extra container for each form > > component with dynamic visibility. > > I agree with Igor. We use EnclosureContainer for the complicated cases > but using wicket:enclosure is really nice for simple things and we use > it a lot. > > Would it be possible to emit warnings when using wicket:enclosure is > buggy? I don't if it's possible to detect these cases. > > -- > Guillaume >
