SOLVED: Navigating from IE Mode site to non IE Mode site loses Jump Anchor Link

[bmoteria]

Hello,

We're facing an issue where "Jump Anchor Link" is lost when navigating from IE Mode site to non IE Mode site.

For example, the IE Mode site (https://www.domain.org/) contains following anchor tag:

<a href="https://www.sub.domain.org/something/2#getting-started">Getting Started</a>

When clicking on "Getting Started" link, the page is navigated to "https://www.sub.domain.org/something/2". The suffix "#getting-started" is lost.

It works fine when pasting "https://www.sub.domain.org/something/2#getting-started" url into new tab. The page is scrolled to div container with id "getting-started".

Is there a way to fix this issue?

Versions Tested:

• Microsoft Edge Enterprise - v81.0.416.58
• Microsoft Edge Enterprise Beta - v81.0.416.62
• Microsoft Edge Enterprise Dev - v84.0.488.1

Thanks,

Bishan M.

[#2]

@bmoteria Thanks for reporting this. We are looking into it and will get back to you.

[#3]

@Shilpa_Subramanian Thank you for the update. We look forwad to hear back.

[#4]

@Shilpa_Subramanian any update on this one? Thanks.

[#5]

@bmoteria Thanks for your patience! This issue was fixed for Win 10 1809 and higher in a recent OS update - July 21, 2020—KB4559003 (OS Build 17763.1369) (microsoft.com). 

[#6]

@Shilpa_Subramanian Thank you for your response! I am currently on Win 10 1909 (OS build 18363.959). It responses the same way as I described in the original post. Am I supposed to take any additional action to get this working?

More information:

• Internet Explorer mode API version: 10
• Microsoft Edge version: 84.0.522.58 (Official build) (64-bit)
• Windows version: Windows 10 OS Version 1909 (Build 18363.959) (64-bit)
• Internet Explorer mode adapter version: 84.0.522.58 (dual_engine_adapter_x64.dll)

Thanks,

Bishan M.

[#7 · Accepted solution]

@bmoteria Can you try updating to 18363.997? July 21, 2020—KB4559004 (OS Builds 18362.997 and 18363.997) (microsoft.com)

[#8]

@Shilpa_Subramanian I updated to 18363.997 and it fixes the issue!! Thank you for getting it fixed. :smiling_face_with_smiling_eyes: