Please help test: Angular 1.3, improved transitions, cached views, etc

@adam I’m not sure that I could replicate it with a codepen. There is a thread on it, on here. I can diagram what is happening though.

----------------------------1
---------------2-----------3-----------4
-----------5–6--7-----8–9

Those are the stacks I’m using to navigate. 1 is an abstract parent, as are 2 and 3. States 4 -9 actually show the content. If I am in states 5 or 6 and attempt to go to state 4 I can see the code going to state 4, then it calls state 7, and finally makes a call to whatever state I am attempting to navigate away from. The same thing happens if I am in state 8 going to state 4. It calls 4, then 9, then back to 8. Interestingly if I am in 7 or 9 the state changes to 4 with no issue. I wll update this post with the link to the other thread momentarily. Here is the link: Linking to states in tabs