[
https://issues.apache.org/jira/browse/WICKET-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emond Papegaaij resolved WICKET-5682.
-------------------------------------
Resolution: Fixed
Fix Version/s: 6.18.0
7.0.0-M3
Fixed by adding a special case for 'load' on window, which registers a load
listener wrapping the code in a domready listener. Both normal order (domready
-> load) and reversed order (load -> domready) now trigger the onload code.
> 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
> Fix For: 7.0.0-M3, 6.18.0
>
>
> 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)
