[
https://issues.apache.org/jira/browse/WICKET-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109182#comment-14109182
]
ASF subversion and git services commented on WICKET-5682:
---------------------------------------------------------
Commit 82d40d499c6d89fbd565492fa4098553a47c6ddd in wicket's branch
refs/heads/master from [~papegaaij]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=82d40d4 ]
WICKET-5682: always trigger onload after domready
> AbstractAjaxTimerBehavior fails to trigger
> ------------------------------------------
>
> Key: WICKET-5682
> URL: https://issues.apache.org/jira/browse/WICKET-5682
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.16.0
> Environment: Chrome 36
> Reporter: Emond Papegaaij
> Assignee: Emond Papegaaij
>
> AbstractAjaxTimerBehavior fails to trigger in some circumstances.
> Wicket.Event.add is called to trigger Wicket.Timer.set on the load event. The
> code in Wicket.Event.add adds a domready listener, which registers the onload
> listener as soon as the dom is ready. However, the browser fires onload
> before it fires domready, therefore the registered listener is never
> triggered and Wicket.Timer.set is not called.
> I'm not sure if this behavior is specific to recent versions of Google
> Chrome, but it happens quite consistently (but not always). I think a special
> case for onload is needed:
> $(window).load(function() {
> $(document).ready(function() { ... });
> });
--
This message was sent by Atlassian JIRA
(v6.2#6252)
