Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
http://jsfiddle.net/pauldechov/89S5p/
In root’s connectOutlets, the App still seems un.initialize()d. Is connectOutlets not intended to be used with the root state? (And why?)
If I need something every time the page is loaded (such as in pangratz’s NavigationView here: https://stackoverflow.com/a/11629977/363073), then I will need to have an all-inclusive root.index state like he does?
As pointed out by sly7_7, this is still an open question — apparently the functionality is considered desirable but seems to require an undesirable hack.
http://github.com/emberjs/ember.js/pull/941
For now, either have all your routes in a subroute such as root.index, or manually bind the controller rather than using the outlet helper (e.g.
{{view App.NavigationView controllerBinding="App.router.navigationController"}}).