edge 116 does not work ie mode by enterprise site list(when login edge proflie)
Edge vesrion 116.0.1938.54 (64bit) os : win 10 pro 21H2 When it was not version 116, the ie mode of the edge was used as a list of enterprise sites as a group policy (or registry). However, with the official update to version 116, ie mode's list of enterprise sites does not apply. In edge://compat/enterprise, "emie sitelist cannot be parsed" In edge://policy/, "InternetExplorerIntegrationLevel" and "InternetExplorerIntegrationSiteList" have a status of "error, Ignored" . What is unusual is that this symptom occurs on the PCs of people who connect and use the profile of edge. Even if the synchronization setting is excluded, the enterprise site list does not apply. I must proceed with and use the profile logout unconditionally to apply. I think this is a SW bug... Please correct it as soon as possible...
Clicking link with target="_blank" in IE Mode loses session data in original tab
The problem occurs with the current Edge version 80.0.361.57 (64-bit), but I've also confirmed it is still happening in the latest beta/dev/canary versions as well. We are using IE mode within the Edge browser, and are rendering all pages in IE11 compatibility mode. When left-clicking any link containing a "target="_blank"" attribute in an IE mode-enabled page within our intranet, the destination is successfully opened in a new tab. However, the state of my original tab (as well as the new tab) is effectively logged out and back in, and my session is reset. I have a new ASP and ASP.NET session ID, and all of my session variables are lost. In contrast, if I remove the target="_blank" from the link and do a Ctrl+Left click to open in a new tab, maintaining the session is fine in both tabs. I can also use Javascript to get around this problem, using something like onclick="return ! window.open(this.href);" to open in a new tab yet keep my session in tact. Is this a known issue, and if so, is there a fix in the works?Invitation: Join App Assure for a live Q&A on June 30 on how to configure IE mode wit Microsoft Edge
Did you know that Internet Explorer will retire on June 15, 2022? Over the last year, you may have noticed Microsoft is moving away from Internet Explorer (IE). Microsoft Edge with IE mode is the next step to provide your organization with a more modern browsing experience. Give your organization the dual engine advantage by moving to Microsoft Edge. Microsoft Edge with Internet Explorer mode will replace the Internet Explorer 11 desktop app. Join us on June 30 th at 11 am PST and 6 pm PST to learn how your organization can do the following: Easily deploy and configure Microsoft Edge for improved compatibility Streamline productivity and retain value Increase security Click here to reserve your spot to learn how you can deploy and configure Microsoft Edge today! (EMEA and Americas) Click here to reserve your spot to learn how you can deploy and configure Microsoft Edge today! (APAC)Confusing "back & forward" logic when switching IE mode
Sorry for my poor English. In China, because some websites are still developed using outdated old technologies, the IE mode in Microsoft Edge will be used more frequently. But I think Microsoft Edge's IE mode has a logic that may confuse users in the forward and backward functions of tabs. To put it simply, the same site is loaded in the default mode of Microsoft Edge or refreshed and loaded in the Internet Explorer mode. Both should be regarded as the same page node, not two (that is, one is in Microsoft Edge mode and the other is Internet Explorer mode). Specifically, for example, I opened a new tab, then opened test.com in this tab, and then opened the example.org website in this tab, but I found that this website needs to be switched to IE mode Then I switched from the original Microsoft Edge mode to IE mode manually, it will be refreshed and reloaded in this tab. If I want to go back on this current tab page, then the normal access path should be: example.org (in IE mode, Current Page) → test.com → Default New Page But it actually looks like this in Microsoft Edge: example.org (in IE mode, Current Page) → example.org (Normal Edge mode) → test.com → Default New Page One more jump operation, and this operation is not necessary. The 360chrome browser, like Microsoft Edge, also has a "compatible kernel", the so-called IE mode. There is no problem with the "back & forward" logic of 360chrome browser. Below is the video recorded in these two browsers: (Microsoft Edge Dev 92.0.902.4 and 360chrome 13.0.2250.0, Windows 10 Dev Build 21390) Microsoft Edge Dev 92.0.902.4: https://streamja.com/05PjW 360chrome 13.0.2250.0: https://streamja.com/1OjNv I don’t know if I am the only one in this situation, but I think it may affect the user experience. 360chrome official website: https://browser.360.cn/ee/ Sorry for my poor English. 在中国，因为部分网站仍然使用过时的旧有技术开发，所以 Microsoft Edge 中的 IE 模式会使用得较为频繁。但我认为 Microsoft Edge 的 IE 模式，在标签页的前进和后退功能上，有一个可能会令用户感到困惑的逻辑。 简单来说，站点在 Microsoft Edge 默认模式下加载还是在 Internet Explorer 模式下刷新加载，都应该被视为是同一个页面节点，而非两个（即一个是 Microsoft Edge 模式的，一个是 Internet Explorer 模式的）。 具体来说，举个例子，我新建了一个标签页，然后在该标签页打开了 test.com，然后再在这个标签页打开了 example.org 网站，然而我发现这个网站需要切换到 IE 模式下才能正常访问，然后我手动从原本的 Microsoft Edge 模式切换到 IE 模式刷新当前标签页重新加载。如果我要在这个当前的标签页上后退，那么正常的访问路径应该是： example.org (in IE mode, Current Page) → test.com → Default New Page 但实际在 Microsoft Edge 中是这样的： example.org (in IE mode, Current Page) → example.org (Normal Edge mode) → test.com → Default New Page 多了一个跳转操作，而这个操作并不是必须的。 360 极速浏览器与 Microsoft Edge 一样，也具有“兼容内核”即所谓 IE 模式。360 极速浏览器的“后退&前进”逻辑是没有问题的。 下面是在这两个浏览器中录制的视频：（Microsoft Edge Dev 92.0.902.2 和 360 极速浏览器 13.0.2250.0，Windows 10 Dev Build 21390） Microsoft Edge Dev 92.0.902.4: https://streamja.com/05PjW 360chrome 13.0.2250.0: https://streamja.com/1OjNv 我不清楚这个情况是否只有我一个人出现，但我认为这可能会影响用户体验。 360 极速浏览器官网：https://browser.360.cn/ee/
IE Mode makes the other Edge windows unusable
Hello Team, Edge Chromium: Version 83.0.478.37 (Official build) (64-bit) Issue: In case a modal window is opened and the user open a new Edge Chromium browser window, the location bar do no consider the keyboard keys like backspace, Enter, arrow keys. How to replicate: 1. Open Edge browser with a website on IE mode 2. Open a Modal window (showmodaldialog) 3. Open a new Edge browser window 4. Try typing something in address bar and modifying the text with either backspace, enter, arrow or ctrl+A keys. 5. The address bar ignores the keys, mentioned in Step-4. @josh_bodner, is it a side impact of the fixes done for modal dialog issue? Can you pass this issue within your team pls?
Is it possible to "nest" Blink and IE Mode frames?
Hi there. This is almost certainly a gigantic stretch but I figured it was worth asking. Consider a hypothetical page where the top-level frame (that is, the page referred to in the address bar) is not in the IE mode list. If this page contains an iframe whose target is a page that does come from this list will it be loaded in IE mode or will it run in Blink? Conversely, if the top-level page is run in IE mode but contains an iframe whose origin would ordinarily be loaded in Blink does that iframe run in IE mode or in Blink? I'm assuming this is done at the tab level (and therefore neither scenario is possible) but I would be thrilled to be wrong about this. I ask because I am presently in the process of migrating an application from an old, internally-developed toolkit that is only (officially) supported in IE to Angular, with the intention of dropping IE support altogether. Presently we're accomplishing this by running the Angular-ized portion out of an iframe. This 'does this thing', if you will, but Angular performs extremely poorly in IE and the old toolkit is very "here be dragons" in newer browsers. This has left us in sort of a 'pick your poison' situation until the migration is complete. The old toolkit also includes a few ActiveX controls (that will ultimately be mothballed) that are seldom used and only used by a small slice of our longest users but said users find these controls to be extremely important. If a proper IE mode configuration allows us to make the IE/Blink distinction invisible to Joe User this would significantly cut down our workload. As a final note/question, we don't really have much other than these controls left to migrate so I'm certainly open to other suggestions with regards keeping the ActiveX controls somewhat available while running the application proper in Blink. Perhaps there's a way to spawn a new IE mode window and we do all the ActiveX stuff that way?
