-
Notifications
You must be signed in to change notification settings - Fork 210
Multiple views sticky state #213
Comments
Hi, I've checked it with version 0.13 and it works fine. |
Adding my plunker with the same problem. Version 0.13 does not have this issue. |
I made a similar example before finding this issue. Select
in that order and you'll end up with 0.0.14 does not work: http://plnkr.co/edit/8GLYjQ?p=preview |
@winniehell both plunks behave the same for me, unless I'm misunderstanding something. |
It is important to have the exact same order as I have written it above for the bug to appear. This works for example:
|
I ran into the same bug. Before I found this issue report I made this plunker. At the same time v0.0.13 works without issues for my plunker. |
+1 in v0.0.14. It works after I switch back to v0.0.13. |
dupe #212 |
@winniehell I believe I have a fix for #217 which fixes your plunker: http://plnkr.co/edit/uu5EQFUEcKrwKnuuqrZv?p=preview Also, it's interesting to note that I can't get your plunker to fail using Chrome. Using Firefox, it fails just like you describe. |
@vellotis your plunker is fixed by removing the "sticky: true" on the |
@juliansniff With a little tweak, your plunker is solved with the fix for #217 Multiple sticky states cannot "share" a named view (in your plunk, they're both trying to use 'main' named view). I pulled the sticky state up to a parent state, then made home and about as children to the parent sticky state. |
I played around with your improved plunker. It still misbehaves. Modified the order of these links: http://plnkr.co/edit/rxsFx0WPxbbu4Yz0WSfD?p=preview |
@vellotis ping, can you confirm please? |
@christopherthielen Sry. I confirm that it is working and you can close the issue. |
Looks good on the plnkr. Thanks for handling it. |
Closing as fixed. |
Hi,
I've have this setup
2.1 nested view
for some reason when changing to state C2 in secondary view the state in Primary view is changed.
Is this a bug or it's not supported to have sticky views in multiple views?
The text was updated successfully, but these errors were encountered: