You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2007/03/18 17:51:09 UTC

[jira] Resolved: (WICKET-365) Go from setVisible(false) to setVisible(true) on a component in ajax does not work

     [ https://issues.apache.org/jira/browse/WICKET-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-365.
----------------------------------

    Resolution: Won't Fix

im closing this now because i dont think this is the way to go. if you feel strongly about it please start a public discussion on @dev

> 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.