[TIMOB-16919] iOS: Z-Index is overridden by most recent change for Views
GitHub Issue | n/a |
Type | Bug |
Priority | Low |
Status | Closed |
Resolution | Duplicate |
Resolution Date | 2014-07-12T06:05:12.000+0000 |
Affected Version/s | Release 3.2.2 |
Fix Version/s | Release 3.2.3 |
Components | iOS |
Labels | ios, z-index |
Reporter | Joshua Rhinehart |
Assignee | Ingo Muschenetz |
Created | 2014-05-05T20:39:33.000+0000 |
Updated | 2017-03-20T22:20:35.000+0000 |
Description
When altering the zIndex of views on iOS, the stack order is placing the most recently updated view on top, rather than the view with greatest zIndex. This works properly when tested on Android. The test case as provided by the customer is as follows:
At creation, set zIndex on views as follows:
A: 10
B: 20
C: 100
D: 200
E: 300
F: 400
At runtime, I want to move C to 1100 and A to 1000. If I perform the steps in that order, A always appears in front of all of the other views, even though logging the zIndex of each view shows that the value is set properly on each (where C should be on top of A).
The work-around is to set the zIndex of A to 1000 before setting the zIndex of C to 1100. In other words, I seem to be able to set the zIndex of an object at runtime as long as I'm setting it to be the frontmost, but I can't effectively "insert" a view into the stack order.
Attachments
Closing ticket as duplicate.