Looks like it’s a bug in the .NET driver. Only solution is to go back to Selenium < 3.141. You may need to experiment with earlier versions of Selenium if you choose to go that route:
Looks like it’s a bug in the .NET driver. Only solution is to go back to Selenium < 3.141. You may need to experiment with earlier versions of Selenium if you choose to go that route: