IE & Edge do not fire the popstate event when the URL's hash value changes

Fixed Issue #3740423


Jul 29, 2015
This issue is public.
Reported by 8 people

Sign in to watch or report this issue.

Steps to reproduce


Repro Steps:

Expected Results:

The popstate event should be fired when the URL’s hash value changes!

Actual Results:

Dev Channel specific:



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Mara P.”

      Changed Assigned To to “Christian F.”

      Changed Assigned To from “Christian F.” to “IE S.”

      Changed Status to “Fixed”

    • This ticket has been marked as “fixed” but I’m definitely still seeing the same bug in IE11-latest and Edge-latest. Please note that this bug is not just about “popstate” event support: it’s specifically about the fact that the popstate event is not trigged when only the #hash portion of the URL changes.

    • What version is this meant to be fixed in? I’m not seeing it fixed here either.

    • Microsoft Edge 25.10586.0.0
      Microsoft EdgeHTML 13.10586

    • Yep, definitely not fixed. Clicking on an [Click Me](#newstate) only causes a hashchange event, no popState. I’m on IE 11.63.10586.0

    • (Preview here doesn’t accurately display what shows up when you submit a comment, looks like it stripped out my html example…)

      Clicking an anchor link with href="#newstate" should trigger a popState event in addition to the hashchange event. It only triggers hashchange in IE11 latest.

    • This bug is also listed on caniuse under Known Issues:

    • Unfortunately I have to confirm, that its not fixed (Edge 13). Even your repro Steps example doesn’t work.

    • I can confirm this is still not working, tested on (the one supplied in the IE 11 Win-7 VM). This is causing me to have to handle window.onhashchange only in IE instances.

      I will file in a new issue as this one is flagged as Fixed

    • We are not working on IE feature bugs any longer unless they are security related. Thank you all for the feedback.

      For the record we are seeing this as fixed in the latest Edge RS1 builds (Edge 14/14393). It is understandable that this might still be broken in later builds (and in IE).

      Please make sure that you check the changelog we have setup when testing repros.  Here is a link to the changelog:

      All the best,
      The MS Edge Team

    • In IE 10 and 11 the popstate event will be fired for a history item after the state has been set with history.pushState or replaceState, including when it is set to null, and only when traversing between two items that have had state set. Once the state is set, the popstate event will fire when the user traverses through the browser history.

    You need to sign in to your Microsoft account to add a comment.

    Sign in