You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ma using lazy loading and there are two modules.
One is main module and another is for sublayout New module. when I am using toaster service and displaying the any message it is displaying once, but when I am going to another page then it's displaying message two time everywhere when I am triggering the message.
Please suggest me how I can fix it. I am not using any share module.
What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar.
What is the expected behavior?
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Angular version: 2.0.0-rc.X
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
The text was updated successfully, but these errors were encountered:
[× ] bug report
I ma using lazy loading and there are two modules.
One is main module and another is for sublayout New module. when I am using toaster service and displaying the any message it is displaying once, but when I am going to another page then it's displaying message two time everywhere when I am triggering the message.
Please suggest me how I can fix it. I am not using any share module.
What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar.
What is the expected behavior?
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: