-
-
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
[Regression] disconnectOutlet can't reach across routes #10606
Comments
👍 also experiencing this on 1.11.0-beta.5 |
My experience is that a controller triggering the disconnect via a triggerAction that hits the application controller fails. My temporary fix was to create a |
Actually, it turns out that I'm needing to call http://emberjs.jsbin.com/xibuvaduzu/1/edit?html,js,output Test 1
Test 2
Close needs to be clicked N number of times, where N is the number of times the outlet was rendered into. |
And here's my temporary fix: bugFixRender: (view, options) ->
@disconnectOutlet(
outlet: options.outlet
parentView: options.into
)
@render(view, options) |
PR #10683 addresses @mutewinter 's comment about stacking multiple calls to render. The original issue reported by @Soliah is a regression and still open. |
Closes emberjs#10478 by changing the way we account for routes that don't do a default `render()`. Fixes issue in comments of emberjs#10606 to make us tolerant of multiple renders on top of each other. Close emberjs#10658 by respecting a non-default template rendered into a main outlet as our own template. Close emberjs#10606 by running disconnectOutlet against all active routes, not just the current one. (*shudder*)
Now I've extended PR #10683 to also close the original issue. |
Closes #10478 by changing the way we account for routes that don't do a default `render()`. Fixes issue in comments of #10606 to make us tolerant of multiple renders on top of each other. Close #10658 by respecting a non-default template rendered into a main outlet as our own template. Close #10606 by running disconnectOutlet against all active routes, not just the current one. (*shudder*) (cherry picked from commit a994491)
Disconnecting an outlet used to work even from a sub route. Now the element doesn't get removed from the DOM.
Modal doesn't get removed In Ember 1.11.0-beta.5: http://emberjs.jsbin.com/dofohetuhu/5/edit
Modal gets removed in Ember 1.11.0-beta.1: http://emberjs.jsbin.com/dofohetuhu/3/edit
Seems to have started from beta.2, after this change ba1d1a6
The text was updated successfully, but these errors were encountered: