Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

EdgeDriver can't create DevToolsSession with CreateDevToolsSession() method #8358

Closed
danielmeza opened this issue May 28, 2020 · 4 comments
Closed
Labels

Comments

@danielmeza
Copy link

馃悰 Bug Report

When initialize the EdgeDriver the property optionsCapabilityName is not initialize since the base constructor is never called, therefor the CreateDevToolsSession method fails with a System.ArgumentNullException: Value cannot be null. (Parameter 'key') exception when called

if (!this.Capabilities.HasCapability(this.optionsCapabilityName))

beacause optionsCapabilityName is null

To Reproduce

Create a EdgeDriver and call CreateDevToolsSession()

Expected behavior

The driver create a DevToolsSession

@jdpurcell
Copy link
Contributor

@jimevans Since you've been working on the DevTools code recently, is this issue still relevant? EdgeDriver is still using the second base constructor in ChromiumDriver that doesn't initializeoptionsCapabilityName.

@danielmeza
Copy link
Author

It's relevant since it will affect any one how use the driver in the same way.

@jimevans
Copy link
Member

I believe this has been fixed in the removal of support for EdgeHTML-based Edge. I'm going to close this issue for now. If it's still a problem in the forthcoming 4.0-RC1 or later, please open a new issue.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Sep 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants