I am currently evaluating Edge Chromium at our school. We are still running an on premise SharePoint 2016 Server and using Internet Explorer to access certain ActiveX functions. Therefore, the integrated IE mode comes in very handy.
However, I am facing an odd problem right now. If I open any Office document by right-clicking and selecting "Open in Office desktop app" the current tab gets closed. Although, the document will be opened correctly I will have to reopen said tab every time I open a document. This procedure does work in both Internet Explorer and Chrome without any problem. Does anyone have a clue on how to resolve this issue?
I have attached the chrome_debug log if this is of any help as well as a screenshot showing how I am trying to open a document.
We have the same behavior in the latest Edge version 80.0.361.66 and ONLY in IEmode. When browsing to an on-premise sharepoint site and opening a Microsoft word or excel document, the current Edge tab closes, but only when you have more then 1 tab open. No solution found yet...
@Gleeman@SimonHessBZP Apologies for the delay and thank you for reporting the issue. We believe we have identified and fixed the issue. However, since it is an IE fix, it will ship as part of the OS updates. At the moment, given the current public health situation we are prioritizing our monthly security updates (Update Tuesday) over all other optional, non-security updates. As a result, this fix is a few months out. I'll provide an update closer to release.
@Shilpa_Subramanian Thank you very much for your feedback. Unfortunately, this issue still blocks the rollout of the new Edge at our organization. Therefore, I really appreciate that the issue should be fixed soon. Is there any possibility to already test it out, e.g. with a current Insider build of Windows 10?
@Jsink We are currently targeting the week of July 20th for an OS update to resolve this issue. The fix is available in Insider builds 20130 or after if you'd like to validate.
@Jsink We are currently targeting the week of July 20th for an OS update to resolve this issue. The fix is available in Insider builds 20130 or after if you'd like to validate.
