First of all, congratulations for Ionic. I played with it the last few days and that’s a really awesome framework! I have build a classic app with tabs and a list in the first one. Navigation was slow when going back to the list due to many pictures but that was before you announced “collection-repeat” stuff. Amazing stuff! The navigation is really fluid now and going back to the collection is at least 3x faster than with the ng-repeat!
But a graphic problem appeared with the “collection-repeat” on iOS (emulator & device). It’s really strange… When I’m going to an element of my collection for the first time, everything works perfectly. The child view loads in the “tab-home”, replacing my parent collection. I can go back to the parent, the controller reloads the data and my scrollbar is still where I left it, perfect.
But when I relaunch this process, touching the same element or another, the view containing the collection displays a fast white screen (view seems empty for ~500ms then the collection is back), then the right-to-left animation displays the child view. Once I went to a child view, bug is always present. On Android 4.1.1, there is no “white flash” because the parent view stays white while playing the transition.
Clarification that may be important: the bug is never present when clicking on the 2 first items of the collection. Maybe because these 2 elements are visible at launch and loaded differently?
Can you help me trying to find out the problem please?
Removing the “slide-left-right” animation on the nav-view seems to remove the bug. “slide-right-left” animation suffers from this bug too but “fade-in” doesn’t.
This hides the problem but the transition would give a better native feeling if working as expected. Again, I don’t have this bug with a classic list (ng-repeat), only using the new “collection-repeat”.
Ok, just checked: doesn’t matter if animation attribute is set to body or on ion-nav-view. Flash only occurs when going to a detail page, not when returning to the list.
Happens on beta6 and the nightly.
Checking to see if this is already flagged as an issue on Github.