[
https://issues.apache.org/jira/browse/WICKET-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478507
]
Igor Vaynberg commented on WICKET-365:
--------------------------------------
i dont really like this. that span can mess with css,etc. if you set something
as invisible it should be invisible.
the regular pattern of dealing with this is to add the invisible component's
parent to the ajax target
> Go from setVisible(false) to setVisible(true) on a component in ajax does not
> work
> ----------------------------------------------------------------------------------
>
> Key: WICKET-365
> URL: https://issues.apache.org/jira/browse/WICKET-365
> Project: Wicket
> Issue Type: Bug
> Reporter: vincent Demay
> Fix For: 1.3, 2.0
>
> Attachments: Component.patch.txt
>
>
> Because no tag is generated by RenderComponent when a component is not
> visible. The attach patch simply generates a <span
> id="ComponentMarkupId"></span> when component is not visible and
> OuputMarkupId true. So we can now use ajax on setVisible(false component)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
