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

AjaxIndicatorAppender removes itself immediately when added via ajax

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.5.0
    • Fix Version/s: 1.5.3
    • Component/s: wicket-extensions
    • Labels:
      None

      Description

      When addding/replacing IndicatingAjaxLink's using ajax in Wicket 1.5.0 it's indicator markup is directly removed when parsing the ajax response. The AjaxIndicatorAppender renders a bit of javascript to the response (when it is an ajax request) to remove previous indicators from the dom (see issue WICKET-722) but in 1.5.0 the execution order of the javascript is different, causing the indicator markup to be added first and the javascript to remove previous versions of the indicator to be run next and thus removing the newly added indicator.

      De ajax debug windows shows that the component is replaced first and then the javascript is run. In 1.4.18 ajax logging shows the javascript run first and then the component gets replaced, resulting in correct behavior.

        Attachments

        1. cancelRenderHead.patch
          1 kB
          Andrea Del Bene
        2. hideIndicator.patch
          0.8 kB
          Andrea Del Bene
        3. myproject.zip
          24 kB
          SoulSpirit
        4. myproject.rar
          21 kB
          Igor Vaynberg
        5. WICKET-4071.patch
          1.0 kB
          Martin Grigorov

          Issue Links

            Activity

              People

              • Assignee:
                mgrigorov Martin Grigorov
                Reporter:
                dries.schulten Dries Schulten
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: