[dotnet] Remove Edge Legacy options #9882
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Kudos, SonarCloud Quality Gate passed!
|
|
Merged in d3b35ef. Thank you for the contribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This change removes the
UseChromiumproperty from EdgeOptions, and removes leftover EdgeHTML-only properties and methods that no longer have any effect with the Chromium EdgeDriver.Motivation and Context
In #9166 the decision was made to remove EdgeHTML support from Selenium 4. Capabilities that were only applicable to MicrosoftWebDriver (EdgeHTML) can safely be removed. Now that Edge Chromium is the default and only supported Edge version, the
UseChromiumswitch and the related EdgeDriverService constructors can be removed as well.Types of changes
Checklist