[jira] [Commented] (WICKET-5464) AbstractAjaxTimerBehavior does not work in combination with Wizards

["Sven Meier (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864483#comment-13864483 ] 

Sven Meier commented on WICKET-5464:
------------------------------------

I agree with the reporter.

With my recent changes on master it should be easier to remove the timer in the browser without actually stopping the AbstractAjaxTimerBehavior.

[~mgrigorov] WDYT?

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