$location.hash() returning empty string

[Lee Owen]

Anchors aren't working in angular using ngViews.  If I log the result of $location.hash() in angular's function scroll() I see that it's getting a value of '' when the url is:  mydomain.com/#/test

Any ideas on why this might be occurring?

[Joshua Miller]

Hi!

Can you provide a jsFiddle or Plunker so we can see your code in context? It'll make things a bit easier on us.

Josh

On Wed, Jan 2, 2013 at 4:23 PM, Lee Owen <itsle...@gmail.com> wrote:

Anchors aren't working in angular using ngViews.  If I log the result of $location.hash() in angular's function scroll() I see that it's getting a value of '' when the url is:  mydomain.com/#/test

Any ideas on why this might be occurring?

--
You received this message because you are subscribed to the Google Groups "AngularJS" group.
To post to this group, send email to ang...@googlegroups.com.
To unsubscribe from this group, send email to angular+u...@googlegroups.com.
Visit this group at http://groups.google.com/group/angular?hl=en-US.
 
 

[Lee Owen]

I'm not sure how to get either jsFiddle or plunkr to allow hashtags.  This is the basic gist of it, yet in my project $location.path() shows the correct path, but $location.hash() is empty despite the path being "/#/whatever"

http://jsfiddle.net/ItsLeeOwen/e3Bvp/#/test

[Lee Owen]

if I log window.location.hash I get the hash result "#/test".  That is in my project, I can't seem to get any hash info from jsFiddle.

[Joshua Miller]

There wasn't any active route URL in that example - it was only working on the `otherwise`. I changed it and now the route, which is the path, works as you'd expect: http://jsfiddle.net/joshdmiller/e3Bvp/2/ .

Josh

On Wed, Jan 2, 2013 at 4:43 PM, Lee Owen <itsle...@gmail.com> wrote:

if I log window.location.hash I get the hash result "#/test".  That is in my project, I can't seem to get any hash info from jsFiddle.

[Lee Owen]

Thanks Joshua!  Why isn't $location.hash() return "/test" while window.location.hash does show "#/test"?  This is where I'm confused.

[Lee Owen]

Additionally if I call $location.hash('test') the url ends up being mangled with double hash symbols as: "##test"

[Lee Owen]

I think that I understand my err.  I thought routes were based on a hash value such as "/#/my/route", but angular considers a route separate from a hash.  '#/my/route' is the path, and a hash would be appended to the end of that to look something like, "#/my/route#myHash".  Correct?

[Joshua Miller]

Yep! You got it. Routes are based on the browser's hash, which means the `window.location.hash` contains whatever information is necessary to identify state in an SPA (say, for bookmarkability). Angular processes this information and makes it available through the $location service. So in order to use hashes as we would in something other than a single-page application, a second shebang is included, everything after which is a gettable/settable from $location.hash(). The guide has more info: http://docs.angularjs.org/guide/dev_guide.services.$location

Josh

On Wed, Jan 2, 2013 at 5:11 PM, Lee Owen <itsle...@gmail.com> wrote:

I think that I understand my err.  I thought routes were based on a hash value such as "/#/my/route", but angular considers a route separate from a hash.  '#/my/route' is the path, and a hash would be appended to the end of that to look something like, "#/my/route#myHash".  Correct?

--