-
Notifications
You must be signed in to change notification settings - Fork 603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS: Keyboard is not resized properly when resize mode is changed from native to none #2216
Comments
This issue needs more information before it can be addressed. Please see the Contributing Guide for how to create a Sample App. Thanks! |
@cornelius-behrend can you provide a GitHub repo with an app where the issue can be replicated? |
@alexgerardojacinto i am also facing the same issue it happens whenever the keyboard.resize function is triggered when keyboard is open resized to native and resized to none after closing the keyboard this issue is mostly replicated in iphones of lower OS or model for example we are facing issue in iphone 7 , 8 , 8 plus etc. so please check it from your side and do the fixes needed a humble request . |
#577 this is the issue i am facing it says that native would fix the issue but it isnt working as expected @alexgerardojacinto |
I resolved the issue by creating a workaround by using this |
Bug Report
Plugin(s)
@capacitor/keyboard 6.0.2
Capacitor Version
@capacitor/cli: 6.1.2
@capacitor/android: 6.1.2
@capacitor/ios: 6.1.2
@capacitor/core: 6.1.2
Platform(s)
Current Behavior
When the keyboard is opened with the resize mode
native
and then the resize mode is switched tonone
while the keyboard is still open, closing the keyboard results in a black box since the web view is not reseted to its original bounds.Expected Behavior
Even when changing the resize mode back and forth, the web view should be displayed correctly.
Code Reproduction
This can be i.e. fixed by adding a reset of the frame if the resize mode is "none".
Other Technical Details
Additional Context
The text was updated successfully, but these errors were encountered: