You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Matej Knopp (JIRA)" <ji...@apache.org> on 2007/11/22 11:45:43 UTC
[jira] Reopened: (WICKET-745) AbstractAjaxTimerBehavior triggered
more than expected after a new Ajax rendering
[ https://issues.apache.org/jira/browse/WICKET-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matej Knopp reopened WICKET-745:
--------------------------------
> AbstractAjaxTimerBehavior triggered more than expected after a new Ajax rendering
> ---------------------------------------------------------------------------------
>
> Key: WICKET-745
> URL: https://issues.apache.org/jira/browse/WICKET-745
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-beta2
> Reporter: Xavier Hanin
> Assignee: Matej Knopp
> Fix For: 1.3.0-beta4
>
>
> When an AbstractAjaxTimerBehavior is rendered in an AjaxResponse due to another Ajax callback than the one triggered by the timer itself, it sends a new setTimeout javascript call to the client, causing the client to call the timer more frequently than expected: x+1 times as expected, where x is the number of times the behavior is rendered in a separate Ajax response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.