-
Notifications
You must be signed in to change notification settings - Fork 13.5k
ion-input: when closing keyboard padding bottom is not removed #5529
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
Comments
This is something that's by design and still something we're working on. Basically when you remove that padding, while the keyboard is also transitioning away, it's extremely janky to the point leaving that padding there is the lesser of two evils. But like I said, we're still working on better solutions. |
Nice to hear that. Many thanks. |
Any news on this one? When it will be tweaked? |
#5432 gets reported again :) @raducostea I'm personally turning off the troublesome ionic keyboard padding and falling back to the device native behavior of letting the whole page slide up and down in the meantime. You might be able to tweak your own app with one of the config workarounds I've identified at: |
...So the issue is just "closed" until further notice? This is actually a huge deal for UX, I'd honestly prefer a little "jank" to having the entire UX of a page changed unalterably once the keyboard goes away... |
im experiencing this same issue |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
Short description of the problem:
ion-input, when tapping on the field, the keyboard shows up.
When closing the keyboard, the bottom padding is not removed so scroll remains same as when the keyboard is open.
Steps to reproduce:
Ionic Version: 2.0.0-beta.17
Browser & Operating System: Android / Chrome
ionic info:
The text was updated successfully, but these errors were encountered: