[TIMOB-3451] Android: TextField in TableViewRow in 2nd Tab in TabGroup loses focus on keyboard display
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Duplicate |
Resolution Date | 2012-05-29T16:56:44.000+0000 |
Affected Version/s | Release 1.7.0 |
Fix Version/s | n/a |
Components | Android |
Labels | SupportTeam, api |
Reporter | Paul Dowsett |
Assignee | Hieu Pham |
Created | 2011-04-15T03:45:20.000+0000 |
Updated | 2017-03-21T22:40:37.000+0000 |
Description
Environment:
- TiDev 1.2.2
- Ti SDK 2.0.1GA2
- Android SDK 2.2
- tested in emulator only
This issue was first discovered by user "JH" in this http://developer.appcelerator.com/question/117540/textfield-on-tableview-loses-focus-android#"> Q&A post
With a textField added to a tableViewRow on a secondary tab, the
user clicks it and the keyboard appears but the textField loses
focus. This is demonstrated by the following code:
var win1 = Ti.UI.createWindow({
title:"Window 1"
});
var tab1 = Ti.UI.createTab({
title:"Tab 1",
window: win1
});
var win2 = Ti.UI.createWindow({
title:"Window 2"
});
var row = Ti.UI.createTableViewRow({});
var tF = Ti.UI.createTextField({
// keyboardType:Ti.UI.KEYBOARD_NUMBERS_PUNCTUATION, // another issue reported in next ticket
width:300
});
row.add(tF);
var tV = Ti.UI.createTableView({data:[row]});
//win1.add(tV); // this works as expected
win2.add(tV); // this demonstrates the issue
var tab2 = Ti.UI.createTab({
title:'Tab 2',
window: win2
});
var tabGroup = Ti.UI.createTabGroup();
tabGroup.addTab(tab1);
tabGroup.addTab(tab2);
tabGroup.open();
The issue does not exist when a tableView or tabGroup are not used, and 1.5.1 exhibits the correct behavior
Changing customer priority to 'within release' as we have customers relying on this requirement. Associated helpdesk ticket: http://appc.me/c/APP-515579
Associated helpdesk ticket: http://appc.me/c/APP-557344 As well as Kitchen Sink sample: table_view_textfield.js
Linking with TIMOB-8332 since the cause appears to be the same and this issue is resolved by the same fix.
The issue exists in the latest master build.
This is the same issue as timob-8332. Resolving as Won't Fix.
Closing ticket as duplicate.