[TIMOB-12710] MobileWeb: Setting 'bottom' and 'right' properties for child elements of 'scrollView' causing strange result.
GitHub Issue | n/a |
Type | Bug |
Priority | Critical |
Status | Closed |
Resolution | Won't Fix |
Resolution Date | 2017-05-01T22:36:38.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | MobileWeb |
Labels | linvalid, mobileweb |
Reporter | Carter Lathrop |
Assignee | Chris Barber |
Created | 2013-02-11T18:46:23.000+0000 |
Updated | 2018-04-04T23:20:26.000+0000 |
Description
*Problem*
MobileWeb: View position is not consistent with expected results in other platforms. See example code and screenshots.
*Steps to reproduce:*
1) open project from attachment.
2) Run it (as mobile web)
*Expected result:*
see expected_in_android.png
*Actual result*
see actual_in_webview.png
*Code:*
{noformat}
var win = Ti.UI.createWindow({
backgroundColor: 'black'
});
var self = Ti.UI.createScrollView({
width : 400,
height : 400,
backgroundColor : 'red'
})
var customView = Ti.UI.createView({
backgroundColor : 'green',
width : 50,
height : 100,
right : 25,
bottom : 50
})
var customView1 = Ti.UI.createView({
backgroundColor : 'yellow',
width : 50,
height : 100,
right : 50,
bottom : 100
})
var customView2 = Ti.UI.createView({
backgroundColor : 'blue',
width : 50,
height : 100,
right : 75,
bottom : 150
})
var customView3 = Ti.UI.createView({
backgroundColor : 'cyan',
width : 50,
height : 100,
right : 0,
bottom : 0
});
self.add(customView);
self.add(customView1);
self.add(customView2);
self.add(customView3);
win.add(self);
win.open();
{noformat}
Attachments
Tested and confirmed bug. It seems that the mobileweb version of views are not being placed in the expected position of its parent. You can see that the for the cyan view where the bottom and right properties are set to 0 but the view is not in the bottom right hand corner.
Resolving ticket as "Won't Fix" as MobileWeb is no longer supported.
Closing as will not fix.