[jira] [Issue Comment Edited] (WICKET-4071) AjaxIndicatorAppender removes itself immediately when added via ajax

["Ivan Vasilev (Issue Comment Edited) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145827#comment-13145827 ] 

Ivan Vasilev edited comment on WICKET-4071 at 11/7/11 9:28 PM:
---------------------------------------------------------------

The issue is still reproducible with myproject.zip - https://issues.apache.org/jira/secure/attachment/12501060/myproject.zip. 
                
      was (Author: hok):
    The issue is still reproducible with myproject.zip - https://issues.apache.org/jira/secure/attachment/12501060/myproject.zip (and in my source also). 
                  
> AjaxIndicatorAppender removes itself immediately when added via ajax
> --------------------------------------------------------------------
>
>                 Key: WICKET-4071
>                 URL: https://issues.apache.org/jira/browse/WICKET-4071
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>    Affects Versions: 1.5.0
>            Reporter: Dries Schulten
>            Assignee: Igor Vaynberg
>            Priority: Minor
>             Fix For: 1.5.3
>
>         Attachments: WICKET-4071.patch, hideIndicator.patch, myproject.rar, myproject.zip
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira