[TIMOB-16704] Android: when showing a listview with a custom template, child elements are displayed incorrectly
GitHub Issue | n/a |
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Duplicate |
Resolution Date | 2014-06-17T20:35:50.000+0000 |
Affected Version/s | Release 3.2.2 |
Fix Version/s | n/a |
Components | Android |
Labels | alloy, android, listview, listviewitem, template |
Reporter | Uriel Arvizu |
Assignee | Hieu Pham |
Created | 2014-03-24T23:26:24.000+0000 |
Updated | 2017-03-22T22:09:42.000+0000 |
Description
In an Alloy Project, when rendering a ListView with ListItems using an external Custom template, sometimes the Views contained in the vertical layout will be rendered not in proper order.
For example, if my template contains a view with a vertical layout and inside it there are two child views, view A and view B, sometimes the order of the two will change, displaying sometimes A first and then B, while other times B will be first and A will be second.
The expected behaviour should be for view A to be displayed always first and then view B should be underneath view A.
I'm supplying two images showing the expected behaviour and the unexpected behaviour, plus a test project, if the items aren't rendered as in the unexpected behaviour image close the app and try again, sometimes it happens the first time and others after 5 or 6 tries.
If the vertical layout is removed then the views overlaps on each other but which view is shown on top changes. For example, sometimes view A will be on top view B, while other times view B will be on top of view A. The expected behaviour here should be first view declared on the xml should be the one on the bottom while the last view declared on the xml should be the one on the top.
The unexpected behaviour happens at an inconsistent rate so it's hard to predict when will it happen or at least I haven't being able to pinpoint what triggers the bug.
Attachments
Moving this ticket to engineering as I can reproduce this issue with the attached test case.
I just want to inform that this ticket hasn't even received a priority level. Can I get some feedback please?
Just to confirm, this is still happening in 3.2.3.GA.
Closing ticket as duplicate and links to the related ticket have been provided above.