The address of the pit is as follows:
- [webview_flutter] Keyboard persists after tapping outside text field #36478
- [webview_flutter] Keyboard language can’t change on Android #41089
Github.com/flutter/flu…
The problem with these pits is that the input method does not disappear automatically and the language cannot be switched automatically.
As a direct result, webViews can only be used for presentation, not for input.
This for many accustomed to the DEVELOPMENT of H5 nested Webview control companies, is undoubtedly a long and smelly pit.
But thanks to the community version of the native WebView Overlay solution, plus the ability to add Flutter — Boost — many engineers have a chance to get out of the hole
Let me see when this big hole can be filled in. This really reflects how open the heart of the Google team is and how capable it really is…