in IE 8 the js(and jquery 1.4.4) from your title example with back button only refreshes title every third click

[MarcCJohnson]

using the exact code (js not HTML) in your example (at http://benalman.com/code/projects/jquery-hashchange/examples/hashchange/) with jquery v1.4.4, in IE 8, the hash is only changing every third time. In firefox it's catching the hash change perfectly.

My thought is that I'd be able to change the hash 20 or 30 times and hit the backbutton and see those changes as I step back through the history in the title. Again that's happening in FF but only one in three times in IE 8.

[cowboy]

I can't reproduce this issue here.

[MarcCJohnson]

I will produce a test script ASAP. By the way I love your work! All cudos
to you and all that you're doing!

On Wed, Jun 27, 2012 at 10:18 AM, Ben Alman <
reply@reply.github.com

wrote:

I can't reproduce this issue here.

---

Reply to this email directly or view it on GitHub:
#20 (comment)

[MarcCJohnson]

Hey Ben sorry to be so long in getting this to you, been busy at work...

To reproduce you must have IE 8 I have version 8.0.6001.18702.

1. Unzip files and throw them in a directory
2. open haschangeTst.html
3. click the different anchors in the left column scrolling back to the
   left column anchors a few times, at least 5. (the event fires here yaay!)
4. after doing this a few times begin clicking the back button.

In Firefox the hashchange event works perfectly each time. In IE 8 the
haschange event only fires once exactly every third click. I did observe
that the windows.onhashchange fires natively in FF but not in my version of
IE 8 (although I thought the property was supported in IE 8), so I think
the issue is in your polling implementation that accomodates browsers that
don't support onHashChange natively.

Hope this is of some use

On Wed, Jun 27, 2012 at 10:23 AM, Marc Johnson marc.c.johnson@gmail.comwrote:

I will produce a test script ASAP. By the way I love your work! All
cudos to you and all that you're doing!

On Wed, Jun 27, 2012 at 10:18 AM, Ben Alman <
reply@reply.github.com

wrote:

I can't reproduce this issue here.

---

Reply to this email directly or view it on GitHub:
#20 (comment)

[cowboy]

Are you viewing the web page at a file:// URL or through a web server at a http:// URL? Because there's often a difference in behavior, especially with code that modifies the page URL.

Please ensure that you are testing this through a web server. Also, be sure to test on a different machine as well, and then report back with your results.

[MarcCJohnson]

I am definitely seeing this on a local apache server. Sorry for not
pointing that out in instructions. That file should definitely be unzipped
to htdocs.

On Tue, Jul 10, 2012 at 6:36 AM, Ben Alman <
reply@reply.github.com

wrote:

Are you viewing the web page at a file:// URL or through a web server at
a http:// URL? Because there's often a difference in behavior,
especially with code that modifies the page URL.

Please ensure that you are testing this through a web server. Also, be
sure to test on a different machine as well, and then report back with your
results.

---

Reply to this email directly or view it on GitHub:
#20 (comment)

[MarcCJohnson]

Also, I did confirm that I'm seeing this behavior on other machines, thanks.

On Tue, Jul 10, 2012 at 6:57 AM, Marc Johnson marc.c.johnson@gmail.comwrote:

I am definitely seeing this on a local apache server. Sorry for not
pointing that out in instructions. That file should definitely be unzipped
to htdocs.

On Tue, Jul 10, 2012 at 6:36 AM, Ben Alman <
reply@reply.github.com

wrote:

Are you viewing the web page at a file:// URL or through a web server
at a http:// URL? Because there's often a difference in behavior,
especially with code that modifies the page URL.

Please ensure that you are testing this through a web server. Also, be
sure to test on a different machine as well, and then report back with your
results.

---

Reply to this email directly or view it on GitHub:
#20 (comment)

[cowboy]

I still can't replicate this issue. Do you have any addons, toolbars or otherwise non-standard settings in your IE8 or Windows?