[
https://issues.apache.org/jira/browse/WICKET-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17043481#comment-17043481
]
Martin Tzvetanov Grigorov commented on WICKET-6750:
---------------------------------------------------
{noformat}
2- This will trigger jQuery machinery with an aborted status
3- We already have logic in there to handle that case... So, things will be
cleaned up{noformat}
If the error callback is called then the cleanup should work fine!
You will need to disable CSP until you fix your application and all Wicket
libraries you use. At the moment just Wicket itself (core/extensions/...) is
fixed, but I guess Wicket Bootstrap & Wicket JQuery UI may have issues.
> add capability to cancel ongoing AJAX requests from client side
> ---------------------------------------------------------------
>
> Key: WICKET-6750
> URL: https://issues.apache.org/jira/browse/WICKET-6750
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-core
> Affects Versions: 8.7.0, 9.0.0-M4
> Reporter: Ernesto Reinaldo Barreiro
> Assignee: Ernesto Reinaldo Barreiro
> Priority: Major
> Fix For: 9.0.0-M5
>
> Attachments: image-2020-02-24-14-35-26-176.png
>
>
> Currently it is not possible to stop an ongoing AJAX request form client
> side. This would be nice to have, on a per channel basis, for use cases such
> as:
> 1- user cancelling a long lasting AJAX upload or other not duration
> predictable AJAX requests?
> 2- add some logic at client side killing long running AJAX requests under
> certain conditions?
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
