You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Frédéric Bertin <fr...@anyware-tech.com> on 2007/07/19 14:43:38 UTC
Re: Going from setVisible(false) to setVisible(true) does not work
without surounding element
Martijn Dashorst wrote:
> So you mean:
>
> Label l = Label("foo", "hello");
> renders:
> <span wicket:id="foo">hello</span>
>
> ... some ajax stuff, or a normal page render:
>
> l.setVisible(false);
> renders:
> <span wicket:id="foo" style="display:none"></span>
not @wicket:id, but just @id, because the Label should have
setOutputMarkupId(true) to be refreshed with ajax
Fred
Re: Going from setVisible(false) to setVisible(true) does not work
without surounding element
Posted by Vincent Demay <vi...@anyware-tech.com>.
Frédéric Bertin a écrit :
> Martijn Dashorst wrote:
>> So you mean:
>>
>> Label l = Label("foo", "hello");
>> renders:
>> <span wicket:id="foo">hello</span>
>>
>> ... some ajax stuff, or a normal page render:
>>
>> l.setVisible(false);
>> renders:
>> <span wicket:id="foo" style="display:none"></span>
> not @wicket:id, but just @id, because the Label should have
> setOutputMarkupId(true) to be refreshed with ajax
Exactly, the goal of the id on a tag is to make wicket-ajax.js able to
find it in the dom in order to replace it
>
> Fred
>