Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » Elevate Web Builder Technical Support » Support Forums » Elevate Web Builder General » View Thread |
Messages 1 to 7 of 7 total |
Android keyboard covers edit input fields |
Mon, Jun 5 2017 4:11 PM | Permanent Link |
thomh | Hi,
I have an EWB app that is run on both iOS and Android. I have some input fields on the lower 50% of the screen. On several Android devices, when the focus goes to the input fields, the soft keyboard is displayed over obscures/covers them. Is there anything that can be done about this? Thanks. // Thom |
Mon, Jun 5 2017 4:53 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Thom,
<< I have an EWB app that is run on both iOS and Android. I have some input fields on the lower 50% of the screen. On several Android devices, when the focus goes to the input fields, the soft keyboard is displayed over obscures/covers them. Is there anything that can be done about this? >> Typically Android device keyboards cause the browser to resize, which will cause the input fields to re-focus and shift the scrolling. Are you seeing the browser resize, or is the keyboard literally covering the browser viewport ? Tim Young Elevate Software www.elevatesoft.com |
Thu, Jun 8 2017 10:07 AM | Permanent Link |
thomh | Tim Young [Elevate Software] wrote:
<<Typically Android device keyboards cause the browser to resize, which will cause the input fields to re-focus and shift the scrolling. Are you seeing the browser resize, or is the keyboard literally covering the browser viewport ?>> Android behaves differently from iOS in this way: I created a test app which contains 15 edit fields. In iOS I can click on the bottom field (15) and the keyboard pushes the viewport up so that edit field 15 becomes visible. On an Android device when I click the bottom field it looks like the attached picture. Seems that the viewport is not pushed up so that it is visible just above the keyboard. // Thom Attachments: Screenshot_Android.png |
Thu, Jun 8 2017 12:19 PM | Permanent Link |
Matthew Jones | thomh wrote:
> On an Android device FWIW, it might be worth specifying the exact device, and the Android version, and the browser. I got very different behaviours on different devices/versions when I did testing of this sort of thing. The differences were known, and it was normally a matter of detecting the "browser" info and coding it specially to cope with it. -- Matthew Jones |
Fri, Jun 9 2017 6:04 AM | Permanent Link |
thomh | "Matthew Jones" wrote:
<<FWIW, it might be worth specifying the exact device, and the Android version, and the browser. I got very different behaviours on different devices/versions when I did testing of this sort of thing. The differences were known, and it was normally a matter of detecting the "browser" info and coding it specially to cope with it.>> Hi Matthew, I have tested this on various Samsung, Nexus and several cheaper models and they all exhibit the same behaviour. And Chrome now seems to be the default browser for Android phones. // Thom |
Fri, Jun 9 2017 7:35 AM | Permanent Link |
Uli Becker | Thom,
> I have tested this on various Samsung, Nexus and several cheaper models and they all exhibit the same behaviour. And Chrome now seems to be the default browser for Android phones. I can confirm what you are seeing. Obviously the viewport is reduced in size, not pushed up. That's why you are seeing scrollbars in your app. Depending of the form's (and its controls) layout the current edit field is not visible any more. Uli |
Wed, Jun 14 2017 1:41 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Thom,
<< In iOS I can click on the bottom field (15) and the keyboard pushes the viewport up so that edit field 15 becomes visible. On an Android device when I click the bottom field it looks like the attached picture. Seems that the viewport is not pushed up so that it is visible just above the keyboard. >> Yeah, I'm not really sure that I can do anything about this. It's not really possible to detect the soft keyboard display as a distinct event in the browser, at least not with any accuracy and without hacking the event manager in EWB to death. I'll have to think about this some more... Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Friday, December 6, 2024 at 05:39 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |