[
https://issues.apache.org/jira/browse/WICKET-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054044#comment-13054044
]
Pedro Santos commented on WICKET-3827:
--------------------------------------
+1 Martin's patch, it's the same change I did here and my project is working
fine so far.
@Igor the markup id persistence between replacements remains untouched, just
transfering others states than id are problematic since we are overriding the
user's component setup.
> 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
