Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-5682

AbstractAjaxTimerBehavior fails to trigger

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.16.0
    • Fix Version/s: 7.0.0-M3, 6.17.0
    • Component/s: wicket
    • Labels:
      None
    • Environment:
      Chrome 36

      Description

      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()

      { ... }

      );
      });

        Attachments

          Activity

            People

            • Assignee:
              papegaaij Emond Papegaaij
              Reporter:
              papegaaij Emond Papegaaij
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: