3 ms·

False - https://blogs.windows.com/msedgedev/2019/05/06/edge-chromium-build-2019-pwa-ie-mode-devtools/ https://blogs.windows.com/msedgedev/2019/05/06/edge-chromi

• ChrisSD 7y ago
  Yes, that's still an IE11 window in an Edge skin. And that blog post specifically calls out "seamless enterprise compatibility" as being the reason for it.
  • lousken 7y ago
    Yes but it'll be left to sysadmins on which sites to enable this mode - "Microsoft Edge uses your existing Enterprise Mode Site List to identify sites which require IE rendering and simply switches to Internet Explorer mode behind the scenes." So user can't just turn it on himself
• kgwxd 7y ago
  Yeah, that will work out as well as "Compatibility Mode" in previous versions. What you'll really get is a whole different browser that has to be tested against with it's own unique bugs to work around.
  • WorldMaker 7y ago
    "IE Mode" is just IE11 virtualized into a tab container, with strict Enterprise-only opt in to it with a specific site list. It won't have the "Compatibility Mode" problems of needing to opt-out through strict DOCTYPES or server headers or trying to figure out magic like it thinks it needs "Compatibility Mode" because it is Monday on a leap year and uses a JS library with the name of the same JS library that would have a leap year Monday problem if it didn't run in "Compatibility Mode", at least. It may prolong some Enterprise's dependency on very old sites or addons they should have weened themselves out of a decade ago, but you can't magically fix sunk costs (or stupid, for that matter).