Wicket
  1. Wicket
  2. WICKET-4071

AjaxIndicatorAppender removes itself immediately when added via ajax

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor 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.

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

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development