-
-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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 chromedriver cast APIs to remote server #7282
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @jwoolley! Thank you very much for this patch --- it'll help a lot of people. Congratulations on your first PR :)
There are a couple of minor nits (basically just moving things to places that are very new) and I'll happily land this!
java/client/src/org/openqa/selenium/remote/codec/AbstractHttpCommandCodec.java
Outdated
Show resolved
Hide resolved
ChromeDriver APIs for interacting with cast devices can now be invoked via calls to remote server. Referenced ChromeDriver APIs: https://chromium-review.googlesource.com/c/chromium/src/+/1401270
Cast/MediaRouter APIs for are Chromium-specific, but not Chrome-specific, so they're now in the appropriate module.
I pushed a commit that addresses the requested changes. I wasn't sure how to resolve the request as the change link is no longer valid. |
Thank you for your patience during this very slow review. Merging now! Congratulations, and thank you! |
ChromiumDriver APIs for interacting with cast devices can now be invoked via calls to remote server. Referenced ChromeDriver APIs: https://chromium-review.googlesource.com/c/chromium/src/+/1401270
X
in the preceding checkbox, I verify that I have signed the Contributor License Agreement