Actually, I've had similar issues. In my case, if your 404 page also loads a template that still requests the same ng-include reference, then it gets stuck in a loop and will crash the browser. It's not necessarily the fault of angular but it would be nice if the ng-include directive knew that it was loading a partial and instead of falling back to the $routeProvider's 404 method, would instead just fail or show a custom message.
On Wednesday, March 26, 2014 11:32:04 AM UTC-6, [email protected] wrote: > > This is not the place for questions like this. idk what your issue is (you > did not describe it or post an example...), but you should be blaming your > own code, not ngInclude -- ngInclude in isolation will NOT crash the > browser on 404 > -- You received this message because you are subscribed to the Google Groups "AngularJS" 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 http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
