Edge Dev Version 149.0.3984.0 (Official build) dev (64-bit) Update
Got this update on Edge Dev today, immediately thereafter its locked up my pc after it applied and i went to open a new tab (had to ctrl+alt+del and end task it) its something specific here as edge stable and beta still work. unsure what's changed or if others have the same issue? diving into logs in just a sec...Bug: News disabled but news notifications still appear on New Tab page
Good morning. A few months back, our organization disabled the news feature for the new tab screen via the M365 admin center's org settings. Even with this feature disabled, the Inspirational and Informational views on the New Tab page continue to show the notification bell with news notifications. This continues to occur on release (91.0.864.59) and beta (92.0.902.22). I'm assuming this is a bug but if there is another configuration setting that we may have missed, I'd love to have that feedback. Thank you!
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?
