[
https://issues.apache.org/jira/browse/WICKET-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865173#comment-13865173
]
Martin Grigorov commented on WICKET-5464:
-----------------------------------------
> onRemove does the deactivation of the timer on the client side, without that
> the timer would still fire regularly
wicket-ajax.js has additional logic to stop timers which components are no more
in the DOM
Can you please provide quickstart application so we can test the improvements ?
Thanks!
> AbstractAjaxTimerBehavior does not work in combination with Wizards
> -------------------------------------------------------------------
>
> Key: WICKET-5464
> URL: https://issues.apache.org/jira/browse/WICKET-5464
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.12.0
> Reporter: Marcus Thiesen
>
> AbstractAjaxTimerBehavior calls stop() in it's onRemove() method. When used
> in a Wizard onRemove is triggered by onActiveStepChanged. This disabled, but
> never re-enables the behavior if the component tree is reused during wizard
> stepping.
> In my opinion it is more correct to disable the frontend timer but keep the
> internal state of the Bahavior as is (or resetting headRendered to false as
> the Behavior is in the pre render state after the onRemove) in order to
> re-enable the Timer when the step using the Behavior is rendered again.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
