Dec 05 2021 10:44 PM
Dec 05 2021 10:44 PM
Dear Microsoft Edge Team, Hello.
After updating Microsoft Edge 96, the UserAgent sent when switching Internet Explorer mode is the same as Microsoft Edge.
Is this behavior a specification?
The UserAgent sent when switching the Internet Explorer mode
If this behavior is a specification, I would like to know how to send an UserAgent of Internet Explorer 11 when switching between Internet Explorer modes.
Dec 06 2021 12:00 PMSolution
@Taichi_Motoki Hi! Do you know if refreshing the page fixes the issue and the expected UA String is sent?
The team is tracking an issue starting in v96 involving IE mode and the wrong UA String. It appears the introduction of the InternetExplorerIntegrationComplexNavDataTypes policy might be a factor. One work around suggested is disabling the InternetExplorerIntegrationComplexNavDataTypes policy (set to 0). If this is the same issue you are experiencing, we can keep you updated regarding the fix. I believe the most recent Canary Channel build released today might already have the fix.
If you have a separate/different issue, I think it might be best to reach out to Support.
https://microsoftedgesupport.microsoft.com/hc/en-us They should be able to gather logs and help investigate your specific case. Thanks!
Dec 08 2021 07:22 PM
Hello, Kelly. Thank you for your reply!
I installed the most recent Canary Channel build(v98.0.1097.0) and confirmed the operation.
And, I confirmed that this issue has been solved!
So, I think this issue will be solved by updating to Edge Stable Channel build v98.
Thank you for teaching me about Canary Channel build!!
Dec 10 2021 10:46 AM - edited Dec 10 2021 10:47 AM
@Taichi_Motoki Hi! I believe our developers were working to backport the fix, I think it might be included in the most recent Stable Build (https://docs.microsoft.com/en-us/deployedge/microsoft-edge-relnote-stable-channel#version-960105453-...) released today in case you want to give it a try. Thanks!
Dec 12 2021 05:11 PM
I confirmed that Microsoft Edge Stabel Build 96.0.1054.53 solves the issue.
I appreciate you sharing this information.