What happened?

I think so long as we're in beta we want to keep existing behavior when users have drivers on PATH, and just warn them things might fail and why.

Users can choose to run old versions of a driver with ignoreBuildCheck(). If we are going to auto-remediate we'll want to check for that value.

The value add here is that the bindings no longer need to manage looking for things on PATH (huge win), and users will get more insight in the console into why things aren't working.

Scenarios

Old Driver on PATH with internet

• Currently without SM: Use driver on PATH (which will error unless ignoreBuildCheck set)
• Currently with SM: Log warning about old driver on PATH, then download and use updated driver
• Selenium 4.11 : Log warning about old driver on PATH and use it (which will error unless ignoreBuildCheck set)

We could check if ignoreBuildCheck is set and error if not, but I don't think that's necessary for the next release.

Old Driver on PATH without internet

• Currently without SM: Use driver on PATH (which will error unless ignoreBuildCheck set)
• Currently with SM: Errors when it can't connect to url
• Selenium 4.11: Same behavior as with internet

Current Driver on PATH without Internet

• Currently without SM: Use driver on PATH (which works)
• Currently with SM: Errors when it can't connect to url
• Selenium 4.11: Use driver on PATH

Current Driver on PATH with internet but invalid proxy

• Currently without SM: Use driver on PATH (which works)
• Currently with SM: Errors when it can't connect to url via proxy
• Selenium 4.11: Use driver on PATH

Logs for each of these scenarios found here — https://gist.github.com/titusfortner/4dadee2f185af4b04d14b105d1b92322