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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[🐛 Bug]: Documentation > WebDriver > Drivers > Options > v4.0 -- code examples differ across programming languages #1983

Closed
zipperer opened this issue Oct 6, 2024 · 2 comments
Labels
bug Something isn't working needs-triaging

Comments

@zipperer
Copy link
Contributor

zipperer commented Oct 6, 2024

What happened?

This is a minor issue.

The code examples in these sections:

differ across programming languages.

For example

  1. in the browsername section, the Java example differs from the Python and Ruby examples. The Java example creates an options object and inspects the browser name attribute, as the section header suggests. The Python and Ruby examples only create the options object.

20241006-selenium-website-codeblock-java-get-options-instance-attribute
20241006-selenium-website-codeblock-python-make-options-instance-and-do-not-get-attribute

  1. in the pageLoadStrategy section, some examples set options and make a driver, while other examples do that and also get a page and quit.

What browsers and operating systems are you seeing the problem on?

Browser: Brave version 1.69.153
OS: MacOS version 12.7.6

@zipperer zipperer added bug Something isn't working needs-triaging labels Oct 6, 2024
Copy link
Contributor

github-actions bot commented Oct 6, 2024

@zipperer, thank you for creating this issue. We will troubleshoot it as soon as we can.


Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

@Delta456
Copy link
Contributor

This issue can be closed now. PR #2010 fixes the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triaging
Projects
None yet
Development

No branches or pull requests

3 participants