-
Notifications
You must be signed in to change notification settings - Fork 598
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
Capacitor Keyboard height incorrect in Capacitor 6 #2168
Comments
those are basically two different issues that were introduced by the same refactor (basically a rewrite) of the plugin. i already created a issue including reproduction repo for "adjustPan on older Androids" here: #2158 The thing about the navigation bar is that it depends on wether you run your app in immersive mode or not. If yes, the webview also covers the navbar space. The plugin should detect that and add the navbar height correspondingly. |
My bad @chriswep GitHub issue search sucks. I started digging into this issue hours ago which that would've popped up. Technically going solely off just the titles this is a different issue though but related so I'll leave this up. |
This issue needs more information before it can be addressed. Please see the Contributing Guide for how to create a Sample App. Thanks! |
I'm not going to do that as I am short on time. I love the work that the OSS community has put into capacitor but all you need to do is read the merged PR for the complaints. There is enough information across the two issues and PR I linked. |
I'm facing the same issue. On 6.0.2, the plugin returns the wrong keyboard. I suppose the navbar is calculated as well. |
Bug Report
Plugin(s)
Capacitor Keyboard
Capacitor Version
6+
Affected Platform(s)
Android all versions, for older versions (Android 9) the bug is even more severe where no keyboard callbacks are made when windowSoftInputMode adjustPan mode is enabled.
Current Behavior
Expected Behavior
Code Reproduction
Other Technical Details
Additional Context
See PR that broke functionality: #1980
The text was updated successfully, but these errors were encountered: