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

Javascript timers not removed when a Component is replaced by ajax

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 6.0.0-beta3
    • 6.0.0
    • wicket

    Description

      The timer's javascript precondition checks that the component (html element) on which is
      attached the timer behavior is still in the DOM document. When a component with a timer behavior is replaced in java in an ajax request by another component without this behavior, this check is not enough. In this case, the component id is still in the DOM (it was replaced by another one by the same id).

      See email thread at:
      http://apache-wicket.1842946.n4.nabble.com/ComponentNotFoundException-when-replace-a-fragment-with-ajax-tp4650898.html

      Attachments

        1. quickstart.zip
          12 kB
          Bertrand Guay-Paquet

        Issue Links

          breaks

          Bug - A problem which impairs or prevents the functions of the product. WICKET-6191 AjaxTimerBehavior will stop after ajax update of component it is attached to

          • Major - Major loss of function.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. WICKET-6523 Two AbstractAjaxTimerBehaviors on same component timeId conflict

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              mgrigorov Martin Tzvetanov Grigorov
              berniegp Bertrand Guay-Paquet
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: