history.go('url') not working in IE7

[John Kotuby]

Hi all,

Just a little javascript problem here. All the documentation I have seen,
besides showing numerics in the example, such as in history.go(-1), also
mention that if a part of the URL is used then the browser will go to the
nearest history entry with that string in the name of the URL.

Now that I come to think of it, there is no mention as to whether that means
forward or backward. I just assumed backward.

In IE7 the history.go(-1) or history.go(-2) works just fine.

When I replace that syntax with history.go('mysite.com/test.aspx'), which is
where history.go(-1) takes me, and I follow the exact same navigation steps
as before when I click the button that fires the JS, the window just sits at
its current url.

Anyone have an idea what I might be doing wrong?

BTW... I have a reason for using history.go. There may be a better way for
what I am trying to accomplish, but for now I need to know why this
documented feature is not working.

Thanks for any help

 

[Hal Rosser]

Hi all,

Just a little javascript problem here. All the documentation I have seen,
besides showing numerics in the example, such as in history.go(-1), also
mention that if a part of the URL is used then the browser will go to the
nearest history entry with that string in the name of the URL.

Now that I come to think of it, there is no mention as to whether that
means
forward or backward. I just assumed backward.

In IE7 the history.go(-1) or history.go(-2) works just fine.

When I replace that syntax with history.go('mysite.com/test.aspx'), which
is
where history.go(-1) takes me, and I follow the exact same navigation
steps
as before when I click the button that fires the JS, the window just sits
at
its current url.

Anyone have an idea what I might be doing wrong?

BTW... I have a reason for using history.go. There may be a better way for
what I am trying to accomplish, but for now I need to know why this
documented feature is not working.

Thanks for any help

I believe the URL needs to exist in the history list.
according to
http://devguru.com/technologies/javascript/10953.asp

 

[John Kotuby]

Thanks Hal,
I discovered that the problem came from my just using a part of the URL that
was in History. Some of the documentation inferred (or maybe I
misinterpreted) that a substring ot the URL, for example not including the
QueryString, would suffice to locate the nearest History entry containing
the substring. At least for IE7 the rule seems to be the entire URL
including the QueryString along with the exact parameters must be used for
history.go('url') to function properly.