I am working on an application that uses AngularJS for front end and uses ASP.NET web api for backend.
The application has an login page UI (user name , password etc) and also a sidebar and menu bar which are hidden until the user logs in. Just after authentication I am also retrieving some data via REST calls to populate the menu bar, nav bar etc. This is achieved by changing the location path to the new URL and also sending a broadcast message for the Nav and Menu bar controllers to act upon. The problem is while we were using AngularJS 1.5.x the navigation from Login page to any authenticated page with Navbar and Menu bar visible used to happen seamlessly even over 'slow' network connections. But after upgrading AngularJS to 1.6.0 or above, sometimes the login UI (i.e user name password screen) is still visible even though the page has navigated to the new URL which is surprising since that's like angularjs is showing UI from two different routes at the same time. My initial though was like this is probably just a race condition, I simply used ngHide to hide the login page content BEFORE doing the navigation, contrast. Surprisingly the problem still exists, although it's slightly reduced now. Can any provide any ideas on where the problem might be ? I tried looking over the changes between angularjs 1.5.x and 1.6.0 but I couldn't any solution. -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
