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
{{ message }}
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
I am having a html page with a angular with angular controller in seperate file. I am bootstrapping in this html page and i have other plain javascript also where I am trying to set the location.hash with a button click. For me hash value in the page url is coming as #/myhash. If i remove angular bootstraping it come correct as #myash. Is there any way to prevent it ? Am I missing something ? Why is bootstrapping making it wrong ?
Thanks for the help
The text was updated successfully, but these errors were encountered:
What is going on here is that the built-in $location service observes URLs and tries to use them for routing. This is exactly what we want in SPAs but usually not what we want in an application which already manages URLs and want to use AngularJS only for a small portion of the page.
There are some work-arounds in #4608 but no "best & official" solution. I hope to look into it in the 1.5 timeframe.
I am having a html page with a angular with angular controller in seperate file. I am bootstrapping in this html page and i have other plain javascript also where I am trying to set the location.hash with a button click. For me hash value in the page url is coming as #/myhash. If i remove angular bootstraping it come correct as #myash. Is there any way to prevent it ? Am I missing something ? Why is bootstrapping making it wrong ?
Thanks for the help
The text was updated successfully, but these errors were encountered: