Forum Discussion
"noframemerging" in Edge is not supported
MicrosoftHi Everyone! IE mode on Microsoft Edge will support nomerge starting in Microsoft Edge version 93. Currently it can be tested in Microsoft Edge v93 Beta channel: Download Microsoft Edge Insider Channels
Please see the FAQ for instructions:
Thanks!
-Kelly
Kelly_Y
We have run into a use case that doesn't work with the "no-merge" option.
- My sites.xml is configured as below:
<site url="xyz.com">
<open-in merge-type="no-merge">IE11</open-in>
</site>
- I've the site https://server1.xyz.com/app open in Edge in IE Mode. I'm in an active session as I am logging in to it.
- An external application opens https://server1.xyz.com/app/page1 in Edge in a new window with the --new-window switch.
Actual behavior: https://server1.xyz.com/app/page1 does NOT merge with the existing server1.xyz.com/app session. Instead, /apge1 opens in a new session and hence, I'm redirected to the login page i.e https://server1.xyz.com/app/login.
Expected behavior: We need https://server1.xyz.com/app/page1 to merge with the existing server1.xyz.com/app session. The /page1 should open as part of that existing session.
Updating the sites.xml as below did NOT resolve this item.
<site url="xyz.com/app">
<open-in merge-type="no-merge">IE11</open-in>
</site>
<site url="xyz.com/app/page1">
<open-in>IE11</open-in>
</site>
Are there any options to make this use case work as per our expectation? Although most workflows require session isolation that works with the "no-merge" option, we do have this one use case which is different.
Thanks.
Darshini
- Kelly_Y
Darshini_Patel Hi! Since you are running into an issue with the specific scenario you mentioned, I think it would be best to either contact App Assure at https://aka.ms/AppAssure or Support
https://microsoftedgesupport.microsoft.com/hc/en-us. Using either of these options, they should be able to gather your information and help investigate your specific case. Thanks!
-Kelly
- Will do - thanks!