This is the setup we use in Azure Pipelines anyway, so I say let's do it. The only reason I could see not to is if @mustjab or @thejohnjansen think the trouble we're having in Azure Pipelines wouldn't occur if we used Selenium instead.

Or if we care about older releases of Edge, I guess.

I don't think that would be worth keeping working, but I'll let @mustjab and @thejohnjansen speak to that.

I have no reason to believe that the issues with Azure Pipelines would not occur if we used Selenium instead, and I also don't think we should worry about older releases of Edge... :-)

So, I think this should be fine.

@gsnedders please go ahead :)

@gsnedders given that we're now using edgechromium on Azure Pipelines it won't matter all that much, but this would probably still be nice cleanup. Lowering prio though.

This is about EdgeHTML (Edge 12-18) and there's a new product called "edgechromium" for Edge 79+. Closing because I don't think we should be doing any cleanup for EdgeHTML, only eventually remove support.