[
https://issues.apache.org/jira/browse/WICKET-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sven Meier resolved WICKET-6191.
--------------------------------
Resolution: Fixed
Fix Version/s: 6.24.0
7.4.0
8.0.0-M1
Actually the idea of this 'feature' was to prevent unnecessary timeouts.
But with WICKET-4689 I think it's just easier to always add the timer when
rendering the head. I don't see a problem with readding the timer now.
> 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
> Fix For: 8.0.0-M1, 7.4.0, 6.24.0
>
> 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)
