Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
8.1.0
-
None
-
None
Description
Hello!
WICKET-6575 introduced a bug in my application.
I explicitly make an Ajax-Call to an invisible component. In my case: this component displays search results as soon as they are available. The call is triggered by a script created by another (visible) component.
The method "canCallListener" already models the behavior of components/behaviors regarding invocations. If you make Ajax-Calls to invisible components you can hook in here (the default-Implementation causes an exception if component is invisible) and make processing possible. This was a consistent server-side API until Wicket-6575.
Please remove the changes of Wicket-6575.
Thanks
Hans