Forum Discussion
"noframemerging" in Edge is not supported
Darshini_Patel Thanks for letting us know that you'd like to see "noframemerging." I'm looping in one of our product team members and will let you know if they have any clarifying questions or insights on this.
Fawkes (they/them)
Project & Community Manager - Microsoft Edge
- Me too. The issue that I have that was not an issue with the "-noframemerge" in IE, but is a very big issue with MS Edge. My situation is that I need to be logged in to one website with one user ID in multiple windows to switch to the function of the website that I need (one for balances, another for the history that causes the balances, and another for the basis for the rate of the balances). So the separate user profiles feature will not work for my situation.
- Kelly_Y
Microsoft
Elizabeth1969 Darshini_Patel Nrein2062 Ulrich_Bernskov esirvys Hello Everyone! (I tried to tag everyone in the thread, apologies if I missed anyone!)
I know this thread has been around for awhile. I wanted to follow up as the team is doing some investigation about nomerge with IE mode in Microsoft Edge. Specifically they are trying to understand better how customers are using nomerge.
Would you be able to answer the following questions?
- For your scenario, do you use the nomerge command-line option, the registry option, and/or the new session option?
- When you are in a scenario that requires nomerge, are you usually using multiple tabs in the same window? If so, are those tabs part of the same workflow?
Hoping you folks can help! Thank you!
-Kelly
Kelly_Y We are using the command line option. We open the new session in a new window, not the multiple tabs within the same window.
Our customers have started migrating to Edge as IE 11 is going out of support. And so, IE 11 as a workaround is not a viable option for the impacted workflows. Has the team at MS come up with a potential workaround? Any details on that if you can share would be appreciated. Furthermore, what's the current status of the progress on this case? We need to know the projected timeline of support for -noframemerging switch in Edge so that we can plan on re-designing the workflows on our end if necessary.
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 EdgeDeleted Another vote here for this feature. Creating some issues with migrating to Edge in our business.
Deleted Do you have an update from the product team?
Darshini_Patel Thanks for following-up. Yes, they have a couple questions for you:
- Re: "With Edge’s multiple profiles feature, this issue is mitigated but not entirely for some of our use cases;" are you comfortable sharing more details about the uses cases not covered by MS Edge's multiple profiles?
- Similarly, can you share which IE mode elements you still need to use?
- And what is the goal/ideal state that you're looking to achieve with this workflow?
Fawkes (they/them)
Project & Community Manager - Microsoft Edge- Re: "With Edge’s multiple profiles feature, this issue is mitigated but not entirely for some of our use cases;" are you comfortable sharing more details about the uses cases not covered by MS Edge's multiple profiles?
The use case is -
(session 1) An end user is logged in to our application in Edge.
(session 2) The user launches one of our desktop applications that requires another session to be created at the same time. Note that multiple of these sessions could be requested at the same time too (user may launch the desktop application one or more times before exiting from the prior session)
(session 3) The user performs an action in Edge from session 1 that creates yet another session.
Session 2 and session 3 are short lived meaning the user could be in and out of them multiple times while still active in session 1. It's important that all of these session do not merge to allow the user to continue to work without needing to re-login to the application. And also, to allow user to perform above actions in parallel.
Currently, the application code launches session 2 and session 3 in Internet Explorer programmatically with the -noframemerging switch to prevent merging this new session to an existing session. But since this option is not supported in Edge, it seems to leave us with only one option which is to utilize Edge's Profiles feature. And the way I envision that would work does not appear to be a clean solution. It introduces an additional step of profiles creation for the customers (users and their IT department); something that they didn’t need to do in IE. In addition, users would always need to open an Edge session (session 1) in a specific Edge profile, that is different than the profile that will be launched programmatically from session 2 and session 3. This could be messy - let's say there are 3 Edge profiles created, named Session1Profile, Session2Profile and Session3Profile. And, users are instructed to launch an Edge session in Session1Profile. Session2 is launched in the Session2Profile from the desktop application code. And, session3 is launched in the Session3Profile.
My concerns are that -
It's not guaranteed that users will always open an Edge session (session 1) in the Session1Profile. This is something that application developer has no control over.
Hardcoding of the profile names in code for session 2 and session 3 workflows. The names can be config driven but still have to be known to the code.
Since there could be multiple session2 sessions, what can be done about that so that they don’t merge with each other and also to other types of sessions?
- Similarly, can you share which IE mode elements you still need to use?
VBScripts and ActiveX
- And what is the goal/ideal state that you're looking to achieve with this workflow?
Ideally, the expectation is that the -noframemerging support gets added in Edge so the use case described above continues to function in Edge.
- Re: "With Edge’s multiple profiles feature, this issue is mitigated but not entirely for some of our use cases;" are you comfortable sharing more details about the uses cases not covered by MS Edge's multiple profiles?
