pushState replaceState history.state bugs.

Not reproducible Issue #3190292


Jun 12, 2015
This issue is public.
Reported by 0 people

Sign in to watch or report this issue.

Steps to reproduce


Repro Steps:


In this demo, there is an iframe in the lower right. Its content is a duplicate of the parent page which is hosting it.
The parent has a row of navigation buttons in the top left of the screen.
The iframe has those same buttons a little lower, to the right.
The parent and iframe are identical code, but are separate files from separate urls.

Experiment #1

Upon opening the web page and doing nothing else yet
(1) you should see history.length=1
(2) click the IFRAME’s [pushState] button a few times. (lower right). Say, advance history.length to 4.
(3) click the PARENT’s [navigate away] button once. (upper left). This should advance the history.length to 5.

Bug: Probably you will now see history.length=1. So clicking the [back] button has no effect. Clicking the browser back button won’t work either. The nav history is simply gone. poof.

Or possibly now history.length=2. That’s the other possibility I’ve seen with IE. If this is what you observe, then click the [back] button and see exceptions are listed there. “Unspecified error.” That’s what gets thrown just by reading history.state at this point.

Expected Results:

to not lose browsing history
to not throw “Unspecified error.” simply from reading history.state

Actual Results:

Dev Channel specific:



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Mara P.”

      Changed Assigned To to “Travis L.”

      Changed Assigned To from “Travis L.” to “IE S.”

      Changed Status to “Not reproducible”

    • Hello,

      Thank you for providing this information about the issue. After thorough testing, we are unable to reproduce this problem in Edge. Please test this behavior in our latest creator’s update 15063 or the insider build 16199.

      Best Wishes,
      The MS Edge Team

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

    Sign in