[TIMOB-11918] Android: TableView - Textfields covered by keyboard when invoked second time.
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Duplicate |
Resolution Date | 2012-12-17T23:42:47.000+0000 |
Affected Version/s | Release 3.0.0 |
Fix Version/s | Release 3.1.0, 2012 Sprint 26 API, 2012 Sprint 26 |
Components | Android |
Labels | api, qe-and100112 |
Reporter | Anshu Mittal |
Assignee | Ping Wang |
Created | 2012-12-01T10:31:24.000+0000 |
Updated | 2013-03-04T09:59:35.000+0000 |
Description
Textfields covered by keyboard when invoked second time.
This is not regression since the issue occurs as far as 2.1.2 as well.
Steps to reproduce:
1. Create an app using the code below.
2. launch the app and tap on password field to bring up the soft keyboard.
3. click done or hardware back button to bring down the keyboard.
4. Again tap on the password field.
Expected:
The keyboard should pop up but textfields(Username and Password) should not be covered by the keyboard.
Actual:
The keyboard covers both text fields when invoked second time clicking on password field.
var win1 = Titanium.UI.createWindow({
title:'Tab 1',
backgroundColor:'#fff'
});
var data = [];
var txtUsername = Ti.UI.createTextField({
left: 10,
right: 10,
hintText: 'Username',
borderWidth: 0,
borderStyle: null
});
var rowUsername = Ti.UI.createTableViewRow({});
rowUsername.add(txtUsername);
data.push(rowUsername);
var txtPassword = Ti.UI.createTextField({
left: 10,
right: 10,
hintText: 'Password',
borderWidth: 0,
borderStyle: null
});
var rowPassword = Ti.UI.createTableViewRow({});
rowPassword.add(txtPassword);
data.push(rowPassword);
var view = Ti.UI.createScrollView({
contentWidth: 'auto',
contentHeight: 'auto',
height:480,
width:320,
bottom:0
});
var table = Ti.UI.createTableView({
top:200,
height: 200,
style: Ti.UI.iPhone.TableViewStyle.GROUPED,
backgroundColor: 'transparent',
rowBackgroundColor: '#FFFFFF',
allowsSelection: false,
scrollable: false,
data: data,
moving:false
});
view.add(table);
win1.add(view);
win1.fullscreen = true;
win1.open();
Closing this since it is a duplicate of 'Won't fix' bug.