Closed holmesal closed 10 years ago
Hiya @holmesal, fa-index is used to solve this exact problem. It turns out the order that sibling elements are compiled by Angular is inconsistent across browsers and even sometimes within the same browser.
You can pass fa-index
an explicit index and ViewSequence-backed views like the ScrollView will use those indexes for sorting children. (If fa-index is omitted, order will be bound to $index
if that value exists on a given scope, e.g. with ng-repeat, and will be undefined otherwise)
So add fa-index="an-appropriately-sortable-number"
to your fa-view
s and you should be good.
Awesome! That did the trick for me. :+1:
Hiya! I'm trying to lay out a bunch of views in a scroll view, and I'm having some problems with the order.
What I have is this:
Unfortunately, the final fa-view gets displayed amidst the ng-repeated fa-views. What I see is this:
Interestingly, on desktop the final fa-view always shows up in the middle of the ng-repeated views, on mobile it always shows up above all of the ng-repeated views. Always in the same place on each platform.