Feature and motivation

Moving forward, Selenium plans to update implementations to use WebDriver BiDi instead of WebDriver Classic if BiDi is enabled.

It was decided at the Selenium Dev Summit that we would implement the navigation commands with BiDi in all the bindings as the minimum for Selenium 5. This will act as a proof of concept that a user can successfully use either BiDi or Classic depending on the capabilities that are set. We do not need to implement everything in BiDi spec before releasing Selenium 5, just have a working module as a pattern to work from.

Considerations

• let's not worry about making sure we're storing the browser context id properly everywhere for this issue
• we do need to make sure we're looking at the user's page load strategy to determine how to wait for the navigation

Implementations

• .NET — [dotnet] implement WebDriver BiDi with WebDriverBiDi dependency #14052