3 ms·
This stuff happens over time. It is a result of cascading dependencies. Companies have lots of pieces of software that they support for extended periods of ti
by kube-system 7y ago
This stuff happens over time. It is a result of cascading dependencies.
Companies have lots of pieces of software that they support for extended periods of time. Also, they typically avoid requiring users to use different browsers for different applications. The number of support calls goes up dramatically if you need users to use different browsers, and it causes usability headaches when linking from one system to another, because you can only have one default browser. If you bring a piece of enterprise software into any organization, they will want you to target the browser they're using.... so, targeting IE was written into the requirements well after it was a good idea, because legacy compatibility was required. That, of course, works until MS throws a wrench in the works and discontinues the browser.
SaaS will change this somewhat, because the software is continually updated by the vendor. It's mainly on-prem and/or custom applications that cause this issue, because they don't get upgraded until big bucks are dished out.
- gsnedders 7y ago> The number of support calls goes up dramatically if you need users to use different browsers, and it causes usability headaches when linking from one system to another, because you can only have one default browser. Which is precisely why Chromium-based Edge has an IE Mode that uses Trident for given sites so that those legacy systems can be filtered to use a different browser engine from within the same browser UX.
- kube-system 7y agoGood to know -- I personally haven't dealt with this issue in the past few months (or years), but hopefully this will give some organizations a path forward. Between ~2010 and the January release of Edge this year, a lot of organizations were dealing with the scenario I outlined. Although as recently as this month, I've run into scenarios where Chromium-based Edge acts a bit differently than Chrome... so it's not a solid solution in all cases.
- gsnedders 7y ago> Although as recently as this month, I've run into scenarios where Chromium-based Edge acts a bit differently than Chrome... so it's not a solid solution in all cases. I mean the Edge team will treat any such case as a bug if you report it.