Good 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.
> 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.
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.