-
Notifications
You must be signed in to change notification settings - Fork 14
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add webdriver context and make it available from the Browser instance #262
Labels
feature
New feature
Comments
DmitryBogatko
pushed a commit
that referenced
this issue
Sep 17, 2024
DmitryBogatko
pushed a commit
that referenced
this issue
Sep 17, 2024
…ity-selenium-dotnet into #262-add-drivercontext
DmitryBogatko
pushed a commit
that referenced
this issue
Sep 17, 2024
DmitryBogatko
pushed a commit
that referenced
this issue
Sep 17, 2024
DmitryBogatko
pushed a commit
that referenced
this issue
Sep 17, 2024
DmitryBogatko
pushed a commit
that referenced
this issue
Sep 17, 2024
DmitryBogatko
pushed a commit
that referenced
this issue
Sep 18, 2024
DmitryBogatko
pushed a commit
that referenced
this issue
Sep 18, 2024
DmitryBogatko
pushed a commit
that referenced
this issue
Sep 18, 2024
DmitryBogatko
pushed a commit
that referenced
this issue
Sep 19, 2024
DmitryBogatko
pushed a commit
that referenced
this issue
Sep 19, 2024
DmitryBogatko
added a commit
that referenced
this issue
Sep 20, 2024
* [#262] made Browser constructor with DriverService parameter with null by default --------- Co-authored-by: dmitry.bogatko <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Provide access to DriverService and potentially any others objects which are involved into webdriver instantiation.
With access to DriverService you can get chromedriver process id and manipulate with it if needed (like kill in teardown is selenium.quit() does not work for some reason).
The text was updated successfully, but these errors were encountered: