Forum Discussion
"noframemerging" in Edge is not supported
Deleted
We have the same issue. It only occurs when we use IEMode. If we choose to open in native IE we can have multiple sessions with individual logins.
We have the registrysetting for NoFrameMerge *(FrameMerging=Dword0) which is honored when using native IE. But it does not function when using IEMode from Edge.
Ulrich_Bernskov Thanks for letting us know, and welcome to the MS Edge Insider community! I've also shared your perspective with the team and will let you know if/when they have any updates after finishing their discussion.
Fawkes (they/them)
Project & Community Manager - Microsoft Edge
- esirvysNov 10, 2020Copper Contributor
Deleted Another vote here for this feature. Creating some issues with migrating to Edge in our business.
- Nrein2062Feb 26, 2021Copper Contributor@Deleted and another vote for this feature. Thanks.
- Ulrich_BernskovNov 10, 2020Copper Contributor
We found a simple solution for this.
We use a combination of GPO and EMIE lists.
1) Force all sites to be opened in Edge via GPO
2) Define EMIE lists for the sites that should open in IE
3) Inform users to start IE for sites needing 'noframemerging' - any other links will open in Edge.
This makes the actual IE launch for those pesky sites where a full IE functionality is needed.
- HajurbaOct 07, 2020Copper Contributor
Deleted Any update on this. we also need this feature to work.
- Ulrich_BernskovMay 04, 2020Copper Contributor
Deleted Appreciated
If we could influence the launch of IE from Edge with piping flags to the launch like:
C:\program..(x86)\...\IExplorer SCODEF: CREDAT APID:MSEdge -NOFRAMEMERGING
it would also work.
Or add it as a flag in "edge://flags"
- AMarsdenMay 29, 2020Copper Contributor
can I add a "me to"?
our Use Case is similar.
We have a desktop program where the code can open a Document Management System (DMS) passing a case reference. When it does this it is hard coded by the suppliers to open the DMS with a generic read only account.
At other times in the day the users need to be able to add/edit documents so go into DMS as there specific account.
Without - noframemerging on the command that opens from the program they need to make sure all versions of IE are closed prior to opening it with their own credentials.
Cheers
ACM
- BderagischJun 25, 2020Copper Contributor
AMarsden One more "me too". In my case, I have an external application portal we use with our customers. In many cases, my users need to log on to the same portal with different accounts, in support of either different customers or different locations of our business.
-nomerge (even in IE11) worked great, as the identity in one session was not merged with any newly launched browser sessions, so the users can log in with different accounts simultaneously. With Chromium Edge, I need a way for the users to launch "the same" Edge icon, but NOT have the guid merged between sessions, so they are unique.