[TIMOB-14695] Android: Different Behaviour of Hide Soft Keyboard on Android tablet and phone
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Invalid |
Resolution Date | 2013-08-07T19:21:43.000+0000 |
Affected Version/s | Release 3.1.2 |
Fix Version/s | n/a |
Components | Android |
Labels | qe-3.1.2 |
Reporter | Priya Agarwal |
Assignee | Ingo Muschenetz |
Created | 2013-07-30T11:54:32.000+0000 |
Updated | 2013-08-08T11:30:43.000+0000 |
Description
Steps to Reproduce:
1.Install and launch KS.
2.Go to Base UI > Hide Soft Keyboard (Android)
3.Tap inside the text field
4.Tap on Request Hide keyboard
5.Tap inside the text field to bring up the soft keyboard and then click android home button.
6. On Relaunch the KS App.
Expected result.
3.Soft keyboard should pop up
4.Soft keyboard should disappear
5.The app should go in the background and the soft keyboard should also get hide.
6.The soft keyboard should be hidden.
Actual Result on tablet(Nexus7(v4.2.1) for after step 6
The soft keyboard appears it is not hidden.
Actual Result on phone(Samsung Galaxy Note(v2.3.6) for after step 6
The soft keyboard is hidden.
For Step 6 their is difference of Behaviour of Hide Soft Keyboard on Android tablet(The soft keyboard appears it is not hidden) and phone( The soft keyboard is hidden)
It is working as Expected on phone(Samsung Galaxy Note(v2.3.6)) not on tablet(Nexus7(v4.2.1)
Not a Regression as occurs in 3.1.1.GA also
Every Android device handles keyboard differently, please provide test case you followed from TCMS, so we can verify an expected behavior. Tested with: Appcelerator Studio, build: 3.1.2.201307311816 Titanium SDK, build: 3.1.2.v20130801190110 Devices: Nexus7(2) Nexus4 Android version 4.3 KitchenSink version 3.1.1.GA GUID:28a706e9-4130-4acb-bc76-9494255a9279
Unsure of the test case run for this ticket, but the behavior will change based on device and is outside our control once we are backgrounded. It is possible to set a variety of flags with Ti.UI.Android to control this, but it is not going to react the same across all devices and OS versions. See the properties that start with "SOFT_INPUT..." under Ti.UI.Android.
As the behaviour will change based on devices. Hence closing it.