eclipsesource / tabris

Tabris for Eclipse RAP
https://eclipsesource.com/products/tabris
53 stars 18 forks source link

Hide keyboard #441

Open KathrinKieckbusch opened 8 years ago

KathrinKieckbusch commented 8 years ago

We open the keyboard by setting the focus on the textfield. But when we go back to the prvious page the keyboard doesn't hide. We know that problem only on Android. We tried to set the focus on something different and added also a delay but the keyboard is still open. How cann we close it?

ericfischerrv commented 7 years ago

We still have problems with the keyboard and Tabris. As we found out Tabris.js now supports functions to control the soft keyboard, but not the "normal" Tabris unfortunately. Also, there's no bugfix for our problem.

In most cases, we use a numeric keyboard to enter values. Sometimes we have to refresh the content to display some information. If we do that the keyboard changes to a ASCII keyboard but stays active. Bizarrely it doesn't even hide when closing the active page.

20170213_16380620170213_163823

Please excuse the quality of these pictures, but on our devices taking a screenshot isn’t enabled. However, as you can see on the first picture, a ClientDialog is opened. If you press “OK”, the dialog closes itself and the page which has opened it. You can see the result on the second picture. The soft keyboard changed from the desired numeric layout to the ASCII layout and stays visible.

This is what @KathrinKieckbusch reported many months ago, but, unfortunately, nothing happened. Recently, we tried to avoid this bug. First, we tried again to set the focus to another widget or composite to close the keyboard. Therefore we used the setFocus() method. But, again, nothing happened.

After that, we tried to trigger a selection event on a “save” button. Everything worked, the value was stored, but – the keyboard changed to a numeric keyboard and stayed visible.

Finally, we tried to fire a MouseUp event manually on a random label. The event itself was fired but – as we expect – nothing happened to the keyboard at all.

We also thought about triggering the back button to close the keyboard but this function isn’t enabled, too.

This bug is nothing that makes our application unusable but it’s really annoying. As it is right now we can’t publish it to our customers. So, we really need help here. As I said before, Tabris.js has several functions for dealing with the keyboard. It shouldn’t be that problem to fix this bug also in a Tabris version. Also, you could implement some methods to control the keyboard directly.

Hopefully someone will recognize our problem and help us.

Greeting, Eric.

mpost commented 7 years ago

We are currently evaluating how we can bring the tabris.js stream closer to the tabris stream. This will allows us to make improvements in the tabris.js world more easily available in tabris. Please stay tuned for that.

KathrinKieckbusch commented 5 years ago

@mpost what is the current state of this issue?