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

Ronald Cruz commented on WICKET-6840:
-------------------------------------

If it makes any difference (and to further +1 your proposed fix), we integrated 
some JS charting library on our Wicket app as an additional component. This 
component pulled in the library through the <wicket:head> tags and referenced 
it using inline JS.

After the switch to Wicket 9, the initialization for this component failed when 
done through Ajax requests (popping up chart through ModalWindow/ModalDialog). 
Looking at the browser console confirmed that the component's JS was being 
evaluated prior to the JS library being pulled from <wicket:head> causing 
initialization errors and references not found. This was with the CSP disabled. 
The workaround without rewriting the component was to preload the library 
before the component was initialized, but your suggestion solves the root issue.

Anyways, thank you for investigating this Martin.

> 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