Skip to content
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

Fix container view hooks #11425

Merged
merged 3 commits into from
Jun 12, 2015
Merged

Fix container view hooks #11425

merged 3 commits into from
Jun 12, 2015

Conversation

krisselden
Copy link
Contributor

fixes #11077

@rwjblue
Copy link
Member

rwjblue commented Jun 12, 2015

Most of the failing tests are related to RC/AC deprecations and will be fixed by #11428. I'll rebase once that PR is merged.

rwjblue and others added 2 commits June 12, 2015 15:49
The node-managers ensure that `willDestroyElement` (and other hooks)
are called properly (by walking the much more precise `view._renderNode`
tree), having the renderer's `willDestroyElement` also traverse `childViews`
leads to `willDestroyElement` getting called twice in cases other than those
for `ContainerView`.
@rwjblue rwjblue force-pushed the fix-container-view-hooks branch from 3448c68 to 6e8e8ac Compare June 12, 2015 20:49
rwjblue added a commit that referenced this pull request Jun 12, 2015
@rwjblue rwjblue merged commit 4ec788b into master Jun 12, 2015
@rwjblue rwjblue deleted the fix-container-view-hooks branch June 12, 2015 22:37
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

Successfully merging this pull request may close these issues.

[Glimmer] willDestroyElement is sometimes called again when the outlet view destroys the toplevel view
2 participants