-
-
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
this.render and this.disconnectOutlet stopped working in 2.6.0 #13670
Comments
After the initial render, there is no outlet state for dialog, when you open the dialog, it initializes it, at this point we take the isEmpty() path for the outlet. The disconnectOutlet() method does not set it back to empty, but sets it to a state that has only "into", "outlet", "name" with no template key. When you try to open the dialog again, "template" is the only key that is different, but since isStable(old, new) only loops over the old keys, it will never check the template key. I'm not sure which part of this was changed to regress this. |
@krisselden thank you for looking into it and fixing! |
Add failing test for emberjs#13670 and fix render options shaping to fix isStable.
Hi there!
First of all thank you for an amazing work with Ember and its ecosystem, you guys are awesome!
Today I've updated my application to
2.6.0
( together with Ember-CLI, as well as, Ember Data). However, after some testing, I've noticed my dialogs (modals) stopped working on consecutive action.Example:
this.render
this.disconnectOutlet
Here is a Twiddle with replicated issue: https://ember-twiddle.com/ff0aa621c1fde10858b4cc4f1fb62072 As you can see you cannot render dialog component multiple times.
Any help would be much appreciated, thanks!
The text was updated successfully, but these errors were encountered: