Preventing back navigation using onbeforeunload

[Colman]

• I have read the Getting Started section
• I have already searched for the same problem

Environment

Technology	Version
Flutter version	3.19.6
Plugin version	6.0.0
Android version	14
iOS version	N/A
macOS version	N/A
Xcode version	N/A
Google Chrome version	N/A

Device information: Samsung S21 FE

Description

Expected behavior:
Calling _webViewController.goBack() shouldn't modify the navigation history if navigation was prevented on the page using the onbeforeunload JS event.

Current behavior:
The navigation history is modified even if navigation was prevented using the onbeforeunload JS event.

Steps to reproduce

1. Go to any page, then tap a link in that page to bring you to a form. Ensure that the form implements the onbeforeunload JS event to show a "continue without saving" confirmation dialog when back navigation is attempted.
2. Calling _webViewController.canGoBack() returns true. This is correct.
3. Calling _webViewController.goBack() displays the confirmation dialog. This is correct.
4. If "Cancel" is tapped in the dialog, the web view stays on the same screen. This is correct.
5. Calling _webViewController.canGoBack() again returns false. This is incorrect.
6. Calling _webViewController.goBack() again does nothing. This is incorrect.

[github-actions]

👋 @Colman

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!