When virtual keyboard pop up, input box near the screen bottom doesn't automatically scroll up

[raywoocn]

• 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
macOS version
Xcode version
Google Chrome version

Device information:

Description

When there is a input box near the bottom of the screen and we need to input something using the virtual keyboard, when the keyboard is shown, sometimes this input box is hidden by the keyboard, I need the input box automatically scroll up everytime.

Expected behavior:
I need the web page automatically scroll up and make the input box visible to the user automatically as the behavior when we use chrome.

Current behavior:
the input box is not visible most of the time(actually sometimes it works but not always), I need to scroll the web page manually to show the input box.

Steps to reproduce

1. Run the flutter_inappwebview_example app,
2. visit this url: https://www.google.com/advanced_search
3. scroll down and let the site or domain input box near the screen bottom.
4. click on the site or domain input box, virtual keyboard show up.
5. site or domain input box is not visible most of the time(actually sometimes it works but not always), I need to scroll the web page manually to show the input box.
   
   

Images

Stacktrace/Logcat

[github-actions]

👋 @raywoocn

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!