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 2011/06/23 20:37:47 UTC

[jira] [Resolved] (WICKET-3827) Component loses state after replace another one

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

Igor Vaynberg resolved WICKET-3827.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5-RC6

> Component loses state after replace another one
> -----------------------------------------------
>
>                 Key: WICKET-3827
>                 URL: https://issues.apache.org/jira/browse/WICKET-3827
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-core
>    Affects Versions: 1.5-RC4
>            Reporter: Pedro Santos
>            Assignee: Igor Vaynberg
>             Fix For: 1.5-RC6
>
>         Attachments: WICKET-3827-markup-id.zip
>
>
> After WICKET-3197 we set the replacement component 'output markup id' flag to be the same as the replaced component [1]. IMO we can't change the component state set by users in benefit of the component being replaced as it can lead to unexpected behaviors like AJAX links or buttons not working. I'm sending a quickstart to exemplify.
> 1- Component#setMarkupId(Component comp)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira