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

Sven Meier commented on WICKET-6840:
------------------------------------

[~mgrigorov] I'd rather not go back to the previous solution, since I'm quite 
happy how the restructuring in WICKET-6703 worked out.

I've pushed a change that allows components and behaviors to prepend JS again 
in the before-render-phase.
I had to change AjaxIndicatorAppender though - since Behavior#beforeRender() is 
actually called too late (during rendering) and overriding #onConfigure() 
instead.

[~roncruz] Please attach another test-case for your problem with the charting 
library IF it has something to do with #prependJavaScript(). Otherwise open a 
new issue. Thanks!

> Busy indicator persists after request
> -------------------------------------
>
>                 Key: WICKET-6840
>                 URL: https://issues.apache.org/jira/browse/WICKET-6840
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-core, wicket-extensions
>    Affects Versions: 9.0.0, 9.1.0
>         Environment: Linux - Ubuntu 19.10 and centOS. Using OpenJDK 14.
>            Reporter: Ronald Cruz
>            Assignee: Martin Tzvetanov Grigorov
>            Priority: Minor
>         Attachments: test_proj.zip
>
>
> The busy indicator (implementations of `IAjaxIndicatorAware`) appears to 
> persist after the AJAX request finishes. To be precise, It looks like it's 
> not being properly cleaned up, as subsequent requests continue to add new 
> indicators to the page. This looks to be new in Wicket 9/9.1, as I didn't 
> observe the behavior in the past (Wicket 7/8) out of the box.
> I've seen this occur with uses of `IndicatingAjaxLink.java` along with 
> ModalWindow/ModalDialog, but also for use cases of the vanilla 
> `AjaxIndicatorAppender` behavior attached to a component.
> I've attached a small quickstart project which should hopefully make this 
> easy to reproduce. It should suffice to start the project and click any of 
> the two links present.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to