You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 2, 2018. It is now read-only.
In IOS, When i tap and focus an input element the native.keyboardshow event fires and the keyboard pops up. This is absolutely fine.
Then,while the keyboard is up, When tapping another input element and focusing it for some reason the
native.keyboardhide event fires and then the native.keyboardshow fires.
Why does it happen in IOS? and how can i prevent this behaviour so that when one input is focused and the keyboard is up --> focusing another input element would not trigger the native.keyboardhide event??
The text was updated successfully, but these errors were encountered:
vandervidi
changed the title
(IOS) How to stop native.keyboardhide event when focusing an input element?
(IOS) How to stop native.keyboardhide event from firing when focusing an input element?
Feb 17, 2016
ramonornela
added a commit
to zellotec/ionic-plugin-keyboard
that referenced
this issue
Jun 16, 2016
varchecker=true;functionkeyboardShowHandler(e){checker=true;}functionkeyboardHideHandler(e){checker=false;setTimeout(function(){if(checker==false){// do stuff when acually closed}},30);}
vinhbt
pushed a commit
to vinhbt/ionic-plugin-keyboard
that referenced
this issue
Oct 11, 2017
In IOS, When i tap and focus an input element the native.keyboardshow event fires and the keyboard pops up. This is absolutely fine.
Then,while the keyboard is up, When tapping another input element and focusing it for some reason the
native.keyboardhide event fires and then the native.keyboardshow fires.
Why does it happen in IOS? and how can i prevent this behaviour so that when one input is focused and the keyboard is up --> focusing another input element would not trigger the native.keyboardhide event??
The text was updated successfully, but these errors were encountered: