At my company we only recently transitioned from IE to Edge, and all the usual problems that came with it…
Custom applications that only run in IE, different behaviour of Edge and so on.
For our RPA solutions we had to migrate each script to run on Edge. (Ironically the 2021 stable release of UiPath brings a migration tool for it :D) We went old school manual.
For sites/web apps that are compatible in Edge (or other browsers) we had to change:
- selectors for attach and open browser activities
- a few activities that had nested/own browser selectors not inherited by the attach containers
- rebuild any save-as workflow, and upload dialogues as well as alert/messageboxes.
(luckily Edge is very consistent in it’s responses sinces it is based on Chromium so it is easy, just a lot of work depending on the # of scripts you have, and howmuch you rely on self built library activities).
We had one application that had to run in Edge in IE-compatibilymode.
Migration here is slightly different. Your open browser activity still changes, but all selectors around down/upload/dialogue boxes remain the old IE selectors. (So as soon as an app is made compatible with Edge you have to migrate that bot again… jey!)
If your runtime server still has IE available, existing scripts based on IE will continue to work as-is.
You run into trouble when you need to add or update to that script, if you don’t have IE available on your studio environment, unless you build all of your UI selectors by hand, and like testing it out on your production environment afterwards. (A nice expert challenge?)