[TIMOB-2132] Vertical layout broken with auto for height
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Invalid |
Resolution Date | 2011-04-15T03:11:25.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Release 1.5.0 |
Components | iOS |
Labels | defect, ios, iphone, rplist, view |
Reporter | ctredway |
Assignee | Blain Hamon |
Created | 2011-04-15T03:11:25.000+0000 |
Updated | 2017-03-02T21:05:06.000+0000 |
Description
On the iphone using 4.1 and 1.5, if a sub view of a view that uses a vertical layout, the subview will not render.
Modified KS code to show the issue:
var win = Ti.UI.currentWindow;
win.layout = 'vertical';
// HEADER var header =
Ti.UI.createView({height:50,borderWidth:1,borderColor:'#999',backgroundColor:'white'});
var headerLabel = Ti.UI.createLabel({color:'#777',
top:10,textAlign:'center', height:'auto', text:'Header'});
header.add(headerLabel);
win.add(header);
// BODY var body = Ti.UI.createView({height:'auto', layout:'vertical', backgroundColor:'#fff'});
var bodyView1 = Ti.UI.createView({backgroundColor:'#336699',
height:100, left:10, right:10});
var bodyView2 = Ti.UI.createView({backgroundColor:'#ff0000',
left:10, right:10, top:10});
var bodyView3 = Ti.UI.createView({backgroundColor:'orange',
height:50, left:10, right:10, top:10});
body.add(bodyView1);
body.add(bodyView2);
body.add(bodyView3);
win.add(body);
// FOOTER var footer =
Ti.UI.createView({height:50,borderWidth:1,borderColor:'#999',backgroundColor:'white'});
var footerLabel = Ti.UI.createLabel({color:'#777',
textAlign:'center', height:'auto', text:'Footer'});
footer.add(footerLabel);
win.add(footer);
HD ticket for reference:
http://developer.appcelerator.com/helpdesk/view/50001">http://developer.appcelerator.com/helpdesk/view/50001
Marking invalid. Layout:Psychic was requested. I've mentioned that this sort of layout (Where one section compensates for others' positions including size) may be possible with a feature request (to allow percents to be the portion of the remaining space), but that's a feature request, not a bug.
Closed as invalid.