Forum Discussion
Problems with Enterprise Mode (IE Mode) in recent builds ?
I did open a case with MSFT... Unfortunately they did not reach out to me until 5 minutes before EOB for the day. (Of course...) So, I requested a call first thing in the morning on Monday.
In the interim, if Kelly_Y can provide details on what logs I can collect before the call, that would be helpful!
Microsoftjpochedley SteveSta Hello! I'll pass on your observations and how you folks were able to reproduce to the IE Mode team!
jpochedley Thanks for opening a support case! But sorry to hear about the bad timing! 
I'll check with team now to see what type of logs they suggest would be helpful. Thanks!
-Kelly
Kelly_Y We opened a Premier case as well, but still looking forward to you sharing which logs would be best to provide. Thanks!
Found in testing that if a site doesn't load in IE mode on a tab, that tab will never load it in IE mode, nor will it load any site in IE Mode. It's almost as if that tab doesn't know what IE Mode is. You have to open a new tab and try again on that new tab and hope the new tab works with IE Mode.
The opposite is also true, once a tab loads a site correctly in IE mode, any site that is in the XML list for IE mode will work on that tab, even if you use that tab to go to a non-IE Mode site, that tab will leave IE mode for that site as expected, then if you go back to a site on the XML list it will load IE Mode as expected. Issue seems to be related to the tab itself.
I shared this with the engineer working our Premier ticket.
jpochedley Do you happen to see this behavior as well?SteveSta Yes, what you describe has generally been my experience, though again it's not 100% consistent. Occasionally navigating from one IE Mode page (opened incorrectly) to a second IE mode page (opens correctly).... Though I have never seen the reverse... Seems that once a tab understands IE mode, then that tab always works correctly.
I have started working with MSFT on the case. The first thing they asked me to do was install Fiddler and capture the problem. Of course, once I installed Fiddler on two different test machines, I cannot repro the problem at all on either machine. Works 100% correct on the test systems after Fiddler is installed.
