[WICKET-6191] AjaxTimerBehavior will stop after ajax update of component it is attached to

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 7.3.0
• Fix Version/s: 8.0.0-M1, 7.4.0, 6.24.0
• Component/s: wicket
• Assignee: Sven Meier
• Reporter: Vlastimil
• Created: 28/Jun/16 09:26
• Updated: 23/Jan/18 20:10
• Resolved: 28/Jun/16 19:23

Description

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)

Issue Links

• is broken by: WICKET-4689 Javascript timers not removed when a Component is replaced by ajax
• is related to: WICKET-6523 Two AbstractAjaxTimerBehaviors on same component timeId conflict
• relates to: WICKET-5439 Allow restarting AbstractAjaxTimerBehavior without updating its hosting component