-
Notifications
You must be signed in to change notification settings - Fork 27.4k
Update dev_guide.services.$location.ngdoc #3555
Conversation
Added a point about using Angular in the root of a domain with HTML5 urls and then trying to link to external paths within the same directory. Please see the following: Original issue: #3520 (comment) Solution: http://fiddle.jshell.net/fgHf6/3/
Thanks for the PR!
If you need to make changes to your pull request, you can update the commit with Thanks again for your help! |
Just signed the CLA, name is Ashley Taylor |
@zivc - Can you provide a running example of your suggestion? |
@petebacondarwin http://angular.zi.vc/ - In this example, when using an Angular app and HTML5 URLs at the root of a domain - AngularJS tries to route everything even when it's not defined - probably because of our route on See the jsfiddle in the OP for a solution. I was hoping we could get the documentation updated to reflect this. |
Oops sorry. I didn't notice the fiddle. OK. I think the wording could be improved... |
When using Angular in the root of a domain with HTML5 URLs where there are links to external paths within the same directory, the `otherwise` route handler will catch these external files. This can be fixed by prefixing '.' onto the links to URLs that should be handled by angular routing. Original Issue: #3520 Example of Fix: http://fiddle.jshell.net/fgHf6/3/ Closes #3555
Merged with mods. Thanks @zivc. |
When using Angular in the root of a domain with HTML5 URLs where there are links to external paths within the same directory, the `otherwise` route handler will catch these external files. This can be fixed by prefixing '.' onto the links to URLs that should be handled by angular routing. Original Issue: angular#3520 Example of Fix: http://fiddle.jshell.net/fgHf6/3/ Closes angular#3555
When using Angular in the root of a domain with HTML5 URLs where there are links to external paths within the same directory, the `otherwise` route handler will catch these external files. This can be fixed by prefixing '.' onto the links to URLs that should be handled by angular routing. Original Issue: angular#3520 Example of Fix: http://fiddle.jshell.net/fgHf6/3/ Closes angular#3555
Added a point about using Angular in the root of a domain with HTML5 urls and then trying to link to external paths within the same directory.
Please see the following:
Original issue: #3520 (comment)
Solution: http://fiddle.jshell.net/fgHf6/3/