-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[Ember 1.13.1]willDestroyElement never called #11539
Comments
Ember 1.13.2 bumped into the same issue |
same issue. anybody have any luck? |
Updated JSBin: http://emberjs.jsbin.com/pijebi/edit?html,js,console,output It doesn't seem like route backing views are actually destroyed at all. |
Also running into this; it's blocking our upgrade to 1.13 :( |
Any workaround or hotfixes? |
Since this breaks compatibility, can we get a point release for this? |
The fix for this is already in the stable branch, and will be included in 1.13.3. |
Thanks for letting me know, looking forward to 1.13.3. 😃 |
Is there a release date for 1.13.3? I'm waiting for this fix to move some code to production, preferably next week. |
typically we do a weekly release, there is a good chance towards the end of this weekend / early this week. |
Confirm
|
Thanks |
I know the view is deprecated, but shouldnt this still work anyway?
here is a jsbin showing the issue, just change to 1.12.1 to see it work
http://emberjs.jsbin.com/puconuxita/edit?html,css,js,console,output
The text was updated successfully, but these errors were encountered: