You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Vlastimil (JIRA)" <ji...@apache.org> on 2016/06/28 09:26:57 UTC

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

Vlastimil created WICKET-6191:
---------------------------------

             Summary: 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


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)