[
https://issues.apache.org/jira/browse/WICKET-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353568#comment-15353568
]
ASF subversion and git services commented on WICKET-6191:
---------------------------------------------------------
Commit 2678faa0391774058f34779b815c1cbb2e9dd1e3 in wicket's branch
refs/heads/wicket-6.x from [~svenmeier]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=2678faa ]
WICKET-6191 always add timeout when rendered, since wicket-ajax removes any
previous timer
> AjaxTimerBehavior will stop after ajax update of component it is attached to
> ----------------------------------------------------------------------------
>
> Key: WICKET-6191
> URL: https://issues.apache.org/jira/browse/WICKET-6191
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 7.3.0
> Reporter: Vlastimil
> Assignee: Sven Meier
> Attachments: ajax-timer-update-quickstart.zip
>
>
> If you update a component that has AjaxTimerBehavior attached, this behavior
> will not fire anymore.
> See attached quickstart.
> This is due to wicket-ajax-jquery.js:2880 - all timers are removed on
> components DOM node remove (update). But new timer is not scheduled by the
> behavior because it thinks it has timeout already scheduled.
> I propose to add timeout in AbstractAjaxTimerBehavior.renderHead() at all
> circumstances, not only on full page render. (as shown in attached quickstart)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
