[WICKET-6840] Busy indicator persists after request

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 9.0.0, 9.1.0
• Fix Version/s: 9.2.0
• Component/s: wicket-core, wicket-extensions
• Environment: Linux - Ubuntu 19.10 and centOS. Using OpenJDK 14.
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Ronald Cruz
• Created: 13/Oct/20 23:29
• Updated: 15/Oct/20 20:48
• Resolved: 15/Oct/20 20:37

Description

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.

Issue Links

• is fixed by: WICKET-6841 Evaluation order of dependent JS in Ajax request