history.replaceState() doesn't update scroll position state to new hash/fragment, unlike other vendors

Fixed Issue #778040

Details

Created
Sep 2, 2014
Privacy
This issue is public.
Reports
Reported by 0 people

Sign in to watch or report this issue.

Steps to reproduce

URL:

Repro Steps:

JSFiddle test case:

It is also interesting to try visiting the test cases with a fragment
already in the URL. It seems that the history API in IE updates the
page’s address, but doesn’t update “fragment state” – the broken,
second testcase scrolls to #first in spite of displaying #second in
the address bar.

Wikipedia tracking information:
https://bugzilla.wikimedia.org/70176
Deployed ugly workaround:
https://gerrit.wikimedia.org/r/#/c/157165

Expected Results:

The window brings the selection fragment into view

Actual Results:

Dev Channel specific:

No

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Tony S.”

      Changed Assigned To from “Tony S.” to “Eugene V.”

      Changed Assigned To from “Eugene V.” to “Jose L.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “In code review”

      Changed Status from “In code review” to “In progress”

      Changed Status from “In progress” to “In code review”

      Changed Status from “In code review” to “In progress”

      Changed Assigned To from “Jose L.” to “IE F.”

      Changed Status from “In progress” to “Fixed”

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

    Sign in