Skip to content

0.2.17 - $scope '$destroy' of old route now fired after new route controller created #2518

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jamesbrobb opened this issue Feb 3, 2016 · 1 comment

Comments

@jamesbrobb
Copy link

I've just updated to 0.2.17 (from 0.2.15) and it appears to have introduced a bug.

When i navigate to a new route, it's controllers are now created before the '$destroy' event of the $scope of the route controller that's being exited is fired.

0.2.17 example

And this is the previous behaviour

0.2.15 example

@nateabele
Copy link
Contributor

This is a duplicate of #2485. Please see the discussion there. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants