[Feature Request] New parameter to exclude from useShouldInterceptAjaxRequest sync requests.

[EArminjon]

Environment

Flutter version:
Plugin version:
Android version:
iOS version:
Xcode version:
Device information:

Description

What you'd like to happen:

It could be interesting to exclude, from useShouldInterceptAjaxRequest, requests which are sync and not fully supported by the interceptor.

If a web function call an ajax sync request and want to return it's result, using useShouldInterceptAjaxRequest will launch an asynchronous call and this web function will just return "undefined". So, useShouldInterceptAjaxRequest will broke some web feature.

[github-actions]

👋 @EArminjon

NOTE: This comment is auto-generated.

Are you sure you have already searched for the same problem?

Some people open new issues but they didn't search for something similar or for the same issue. Please, search for it using the GitHub issue search box or on the official inappwebview.dev website, or, also, using Google, StackOverflow, etc. before posting a new one. You may already find an answer to your problem!

If this is really a new issue, then thank you for raising it. I will investigate it and get back to you as soon as possible. Please, make sure you have given me as much context as possible! Also, if you didn't already, post a code example that can replicate this issue.

In the meantime, you can already search for some possible solutions online! Because this plugin uses native WebView, you can search online for the same issue adding android WebView [MY ERROR HERE] or ios WKWebView [MY ERROR HERE] keywords.

Following these steps can save you, me, and other people a lot of time, thanks!

[pichillilorenzo]

With the next release, the new setting InAppWebViewSettings.interceptOnlyAsyncAjaxRequests will be available.
It will have true as the default value to not break ajax sync requests.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug and a minimal reproduction of the issue.