You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2012/08/02 11:43:02 UTC
[jira] [Resolved] (WICKET-4689) Javascript timers not removed when
a Component is replaced by ajax
[ https://issues.apache.org/jira/browse/WICKET-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-4689.
-------------------------------------
Resolution: Fixed
Fix Version/s: 6.0.0
> Javascript timers not removed when a Component is replaced by ajax
> ------------------------------------------------------------------
>
> Key: WICKET-4689
> URL: https://issues.apache.org/jira/browse/WICKET-4689
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.0.0-beta3
> Reporter: Bertrand Guay-Paquet
> Assignee: Martin Grigorov
> Labels: ajax, timer
> Fix For: 6.0.0
>
> Attachments: quickstart.zip
>
>
> The timer's javascript precondition checks that the component (html element) on which is
> attached the timer behavior is still in the DOM document. When a component with a timer behavior is replaced in java in an ajax request by another component without this behavior, this check is not enough. In this case, the component id is still in the DOM (it was replaced by another one by the same id).
> See email thread at:
> http://apache-wicket.1842946.n4.nabble.com/ComponentNotFoundException-when-replace-a-fragment-with-ajax-tp4650898.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira