- This topic has 3 replies, 2 voices, and was last updated 11 years, 9 months ago by mreade.
-
AuthorPosts
-
mreadeMemberSupport,
I have a customer who recently purchased my app for use on his Droid3 smartphone. This is the issue he is reporting:
When he taps a field to enter a value, the keyboard pops up. However, it covers the field that he wants to edit. Therefore, he cannot see what he is typing, and the scroll feature does not allow him to scroll the screen to the field to make it visible.
Any thoughts why this might be happening? It does seem to work fine the iOS platform.
mreade
mreadeMemberSupport,
Here is a photo of the Droid3 screen. The user cannot scroll the screen down to get at the input screens. This does work in iOS.
??? Thoughts
mreade
Attachments:
You must be logged in to view attached files.
support-michaelKeymasterThis is a known android bug where the app’s UI webkit transformation settings are not processed correctly when the keyboard is rendered. We have worked on this feverishly for what seems like a zillion hours trying to workaround the bug – including dissecting the android src code. More recent versions of iOS (6) and Android (4.1) have either fixed or significantly improved this bug. For older systems we are working providing some guidance for how to reduce and hopefully eliminate the bug. The dev team reports this is a significant undertaking as it requires a complete implementation of the MobiOne UI layout and transformation services.
In the meantime there aren’t any good options, only less bad. For example this sucks to suggest it but consider laying out the UI such that no fields will naturally occur near the bottom of the screen where the keyboard renders.
mreadeMemberThanks for the prompt feedback Wayne.
That is not good news for sure. But I not sure changing the app layout would work either. Even with the screen at the top, it appears to automatically scrolls it to the point when the field is not in sight.
Changing the screen would include removing too much stuff which would make the information useless to the user.
I’ll hope for the best with your developer’s that they can somehow find the solution.
Thanks,
mreade
-
AuthorPosts