[
https://issues.apache.org/jira/browse/WICKET-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480453
]
Igor Vaynberg commented on WICKET-365:
--------------------------------------
i still dont think this is a way to go. if something is hidden it should not be
rendered!
one) it might be an expensive operation to render it
two) when you do call show on it the markup is not updated at that time, just
made visible, so you will potentially display stale data.
i think the original way is wordier but still the best because it doesnt have
any problems other then wordiness
> 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
> Assigned To: Igor Vaynberg
> Fix For: 1.3, 2.0
>
> Attachments: Component.patch.txt, 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.
