-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Sidenav doesn't show on partial view #473
Comments
Can you open a plunkr with a reproduce case? |
Aye, here it is: http://plnkr.co/F2q4nCgloqnIX7gJjkTL You might need to wait some seconds to see the full view due to heavy scripts inclusions (angular-animate, angulat-route, etc.) |
+1 for this issue. |
Good catch @crrrazymind. The component registry is very old, and was only meant to be a proof of concept. It will be refactored soon. For now, I would advise using data-binding to open and close your sidenav. |
Nice to know what it's about. @ajoslin What do you mean by "data-binding" to open and close the sidenav? |
Use the is-open attribute. It's in the API documentation for sidenav. |
Thank you for explanation, your suggestion works perfectly. |
Element registry is currently kept even after element is removed from DOM. Appart from the memory leak, it also disable future components with same handle from beeing pulled from the registry, for example when users navigate away/back to a page, DOM is reloaded but new component does not work anymore (old registry component is called instead of the new one) @ajoslin reported in referenced issue that registry component will be refactored. Until then, this patch should fix the bug on the component side. Closes angular#473,angular#474
Element registry is currently kept even after element is removed from DOM. Appart from the memory leak, it also disable future components with same handle from beeing pulled from the registry, for example when users navigate away/back to a page, DOM is reloaded but new component does not work anymore (old registry component is called instead of the new one) @ajoslin reported in referenced issue that registry component will be refactored. Until then, this patch should fix the bug on the component side. Closes #473,#474
Element registry is currently kept even after element is removed from DOM. Appart from the memory leak, it also disable future components with same handle from beeing pulled from the registry, for example when users navigate away/back to a page, DOM is reloaded but new component does not work anymore (old registry component is called instead of the new one) @ajoslin reported in referenced issue that registry component will be refactored. Until then, this patch should fix the bug on the component side. Closes angular#473,angular#474
Element registry is currently kept even after element is removed from DOM. Appart from the memory leak, it also disable future components with same handle from beeing pulled from the registry, for example when users navigate away/back to a page, DOM is reloaded but new component does not work anymore (old registry component is called instead of the new one) @ajoslin reported in referenced issue that registry component will be refactored. Until then, this patch should fix the bug on the component side. Closes angular#473,angular#474
When I change view (ng-view) using partials, the sidenav inside my partial view doesn't get toggled (both 'on' and 'off' won't work) unless I reload the whole page.
Any idea?
Code is pretty simple: got a sidenav in the main layout (which currently has no issues) and various (depends on the partial, between 1 and 2) other sidenavs which need a click on a button (with a call on a $scope function) to get toggled.
The text was updated successfully, but these errors were encountered: