-
Notifications
You must be signed in to change notification settings - Fork 13.5k
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
Keyboard Attatchement for Inputs, etc. #9199
Comments
+1. This right here is a major issue. |
Why was this closed? @jqw96 |
It was a duplicate... this issue is still open @cozzbie |
Any updates on this? It's a UI-breaking bug at the moment for any inputs in an ion-footer element. |
Without this fix, creating a chat app with ionic is a pia :( |
Any feedback on this would be extremely appreciated. It's been awesome seeing the advancement of the ionic platform recently, and how it can handle desktop apps now. But there are still major/fundamental issues with your bread and butter mobile solution (which many many users need) that would be great to see fixed/stabilized before new features like the side panel for desktop are released. Is this not being tended to because it's a possible duplicate of this? #10678 |
Any news on input attatchment ?@jgw96 |
Thanks for the issue! This issue is being closed due to inactivity. 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. Thank you for using Ionic! |
Short description of the problem:
Inputs in a footer bar generally do not show when they are active, as the footer bar does in native iOS. Tabs are occasionally raised with the keyboard (50% of the time or so).
What behavior are you expecting?
Active inputs to stick to the top of the keyboard.
Steps to reproduce:
Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
Which Ionic Version? 2 RC2
Run
ionic info
from terminal/cmd prompt: (paste output below)The text was updated successfully, but these errors were encountered: