History API: pushState & replaceState

Confirmed Issue #11373805 • Assigned to Travis L.

Details

Author
Brice C.
Created
Mar 23, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Reports
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

Using history pushState and replaceState correctly updates the URL, however it does not add to the browser history. This prevents SPA type frameworks from having the visited attribute applied to links.

Is Edge and IE blocking the ability for additions to browser history?

Is there any plans to support pushState and replaceState methods similar to how they are implemented in Chrome, Firefox and Safari?

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

    • Hi Brice,

      Thank you for taking the time to submit this issue.

      Edge supports These methods of the History API.

      Would you be willing to provide a repo for us?

      Appreciate the help,

      The MS Edge Team

    • Microsoft Edge Team

      Changed Status to “Not reproducible”

    • Hi Brice,

      I was not able to repro this issue and have not heard back from you.  I will be changing the bug’s state to ‘no repro’ at this time.  If you can provide additional repro information, we will be more than happy to investigate.

      Your feedback is extremely helpful as it helps us to improve the quality of Microsoft Edge.  We continue to welcome more feedback and look forward to hearing from you again soon.

      Best regards,

      The MS Edge Team

    • Changed Status from “Not reproducible”

    • Steven,

      This can very easily be reproduced. If you load Edge or IE to any webpage and then open the console and enter for example history.pushState({}, {}, “/testing”). You will see the URL change and the back and forward buttons will function properly, but the issue is that the state change is NOT added to the browser history. Open the history tab in Edge or IE and you will NOT see an entry for the page "\testing". This prevents SPA like frameworks which use the History API from functioning in Edge or IE like they do in Chrome, Firefox and Safari.

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

    • Hi Brice,

      This was easy to reproduce with the console commands.  Sorry for the delay.  When I don’t get a repro from the submitter it can take longer as many times it isn’t always clear what is being reported, especially when the feature is supported and thought to be working.  In some of these cases I push them to another queue, my process, and return after the bug reports with repro’s have been investigated.

      Also, appreciate the point about the impact to SPA apps (redundant but sounds better?).

      Appreciate your patience and help,

      Steve

    • Microsoft Edge Team

      Changed Assigned To to “Travis L.”

      Changed Status to “Confirmed”

    • history.replaceState(null, null, “url”); is not working on Microsoft edge browser.chrome ,firefox and IE is working good. but issues in only Microsoft edge browser.

    • history.replaceState(null, null, “url”); is not working on Microsoft edge browser.chrome ,firefox and IE is working good. but issues in only Microsoft edge browser.

      history.pushState(null, null, “url”); is not working on Microsoft edge browser.chrome ,firefox and IE is working good. but issues in only Microsoft edge browser.

    • I’m facing this issue. history.replaseState('’, '’, url) does not work correctly, sometimes works, sometimes doesn’t work. history.replaceState itself rewrites current URL on address bar however history object is not modified.
      I tried Edge and IE11, they are same. FireFox, Chrome and Safari work fine.

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

    Sign in