Skip to content

[dotnet] Fix protocol cdp version for remote webdriver#13507

Merged
titusfortner merged 3 commits into
SeleniumHQ:trunkfrom
nvborisenko:dotnet-remote-cdp
Feb 2, 2024
Merged

[dotnet] Fix protocol cdp version for remote webdriver#13507
titusfortner merged 3 commits into
SeleniumHQ:trunkfrom
nvborisenko:dotnet-remote-cdp

Conversation

@nvborisenko

Copy link
Copy Markdown
Member

Description

Regression issue, it fixes determination of cdp version, returned back to the remote webdriver in capabilities.

Motivation and Context

Fixes #13502

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • I have read the contributing document.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@nvborisenko

Copy link
Copy Markdown
Member Author

We also can consider a case when user specified protocol version, then we should not honor se:cdpVersion capability.

@titusfortner

Copy link
Copy Markdown
Member

Oh, I really don't think we should go down the rabbit hole of letting users pick the version. This all goes away whenever we start implementing BiDi. 😄

@nvborisenko

Copy link
Copy Markdown
Member Author

It is the regression issue, just supporting things that has been working. I didn't verified this fix, will be able to do on Monday (01/29).

@nvborisenko

Copy link
Copy Markdown
Member Author

Perfecto! Downloaded artifacts from EngFlow and verified this fix. Works good.

@titusfortner
titusfortner merged commit 5c214ba into SeleniumHQ:trunk Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants