This object is in archive! 

Virtual keyboard handling problem in dialogs

Bucky Kid shared this problem 9 years ago
Closed

Hi menion, there's a still persisting UI problem with virtual keyboard handling so I put it here for the evidence:

In all cases sliding keyboard breaks the displayable range of dialog so that either a very top or very bottom or both can't be accessed by sliding the dialog (while keyboard is visible), probably because decreased visible dialog range is not adopted fully. Plus the worse case when tapped inside a text box in position that is being covered by virtual keyboard, the dialog is moved up including shifting out of screen the top control bar with editing buttons and clipboard buttons, resulting that clipboard operations aren't available. It would be good to fix this.

Replies (16)

photo
1

Bucky Kid, may you please write me also Android version and device you use? Thank you

photo
1

Android is 4.0.4, device is Xperia P

photo
1

Here are screens that illustrate the phenomen (I hope it's not global OS problem):


before entering


nfCMiSl


and after entering


UekDll9 6tkmcLh

photo
1

Thanks,


I've changed one parameter that has anyway influence on whole app, so we will see how it will works here and also in other screens.


New test version is just published, so you may try it once it appear for update

(https://plus.google.com/communities/105669867009952671671)

photo
1

I'm trying version 2.20.2.3 and can confirm that control bar is still being pushed out of screen.

photo
1

I've tested it on three devices, two simulators and everywhere it works correctly for me. One is even older Xperia X8 with 4.0.4


Aren't you using any special custom rom? Otherwise it looks like some special improvement on Sony

photo
1

Hmm, that looks like something wrong is on my device. From more apps I use this screen problem seems only with Locus. Possibly you could connect to it through remote desktop and inspect the problem more precisely. As for ROM it is factory ROM, not customized. Yet there's a chance this may cause another 3rd party app, but I don't remind at this moment to any background app regarding screen adjustments.

photo
1

really only Locus? Interesting. Then I'll try to next version put one more parameter and we will see

photo
1

Menion wrote:

really only Locus? Interesting.

Yes sure, for ex. inplace editing phone contact info which has also long dialog handles the visible range correctly.

photo
1

Hello Bucky Kid, how it looks like in latest version?


I'm trying to find some more info why this may happen and cannot find any, damn.


Is same issue happen to anyone with different device that Xperia P?

photo
1

Hello, sorry for the delay, and I'm still able to reproduce the problem on my phone with Locus 3.1.3.10 and CM Kiktat 4.4.4. Screen height is 960pix.

photo
1

To be true, I'm now not 100% sure, where is a problem.


You can't scroll with content of screen when keyboard appear? And even a changed ROM do not solved this problem? Interesting as I have no other report with similar (or same) problem.

photo
1

The screen is some way "cropped" ie. I can't swipe up-down the whole range of dialog when keyboard slides out. Tried even more keyboards and all do it. So I think this must be something other. I would make a video demonstrating this clearly but can't find any app that records display correctly. Seems only issue with my phone.

photo
2

Hello Bucky Kid,


unfortunately I do not know why this issue happen. It's maybe something in Locus, but seems it's rare problem on some devices, where on other it works correctly. looks like some problem in implementation in CM.


Because it's not serious issue, I'm closing it as "Impossible to solve it" for now. When this issue appear on any of devices I use for testing, I'll try to fix it. Sorry.

photo
1

Good day Bucky Kid,

very old issue and not yet correctly fixed? From what I've noticed during last months (years) on latest Android 6.0+ devices, I never saw such problems again. So I hope I may close this problem as "solved automatically over time"? Or is this happen to You still on any device? Let me know if I may help somehow here. Thanks!

photo
1

Hello Menion, I'm not sure because the old phone where it occured I'm not using as primary now. Also I upgraded Android there to Lollipop so it may resolve. Make it solved, thanks.

Replies have been locked on this page!