[
https://issues.apache.org/jira/browse/WICKET-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478716
]
vincent Demay commented on WICKET-365:
--------------------------------------
Johan : Imho setVisible(false) should not render all the component to avoid the
have a useless heavy html generated code.
Igor : ok, css can make some disturbing thinks on this.
What about adding a style="display:none", style tag always overwrites css,
is'nt it?
I think putting a span tag is good (What is done in cocoon for exemple) because
surounding something with a specific webMarkupContainer to make it visible or
not is very annoying for developpers. On the other hand if you suround with a
parent, it is the same problem because the parent should also have a html tag
associated with disturbing css classes.
> 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
>
>
> 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.
