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]: setWindowRect:true fails when passed to Browser Drivers #13817

Closed
cocchiarocarl opened this issue Apr 12, 2024 · 3 comments
Closed
Labels

Comments

@cocchiarocarl
Copy link

What happened?

When passing in the setWindowRect:true capability to any of the supported Browsers, it fails on all headed Browsers, throwing exception error "invalid" argument: unrecognized capability: setWindowRect". However, it does pass on headless Firefox.

How can we reproduce the issue?

Pass in the setWindowRect:true capability when creating the driver:

ThreadLocal<WebDriver> webDriver = new ThreadLocal<>();
ChromeOptions chromeOpts = new ChromeOptions();

chromeOpts.setCapability(setWindowRect, true);
webDriver.set(new ChromeDriver(chromeOpts));

Relevant log output

"invalid" argument: unrecognized capability: setWindowRect"

Operating System

macOS Sonoma 14.4.1

Selenium version

4.18.1

What are the browser(s) and version(s) where you see this issue?

All

What are the browser driver(s) and version(s) where you see this issue?

All

Are you using Selenium Grid?

no

Copy link

@cocchiarocarl, 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.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

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

Thank you!

@diemol
Copy link
Member

diemol commented Apr 12, 2024

@diemol diemol closed this as not planned Won't fix, can't repro, duplicate, stale Apr 12, 2024
Copy link

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

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

No branches or pull requests

2 participants