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
follow w3c specifications? #237
Comments
RobotJS isn't a web browser, so I don't think the WebDriver spec would apply directly, but you should be able to use |
@1j01 wrap |
By cross-end automation do you mean having code that could run both with RobotJS and a web browser? Or just a familiar API between code that does those separate things? What's the goal? |
driver UI system by w3c webdriver api |
That doesn't clarify anything for me. It would help to know what you're trying to do, specifically, if anything. |
@1j01 Thx |
That would be interesting. It would be pretty easy to create a wrapper project, syntax is being discussed here: #4. |
Well, if not part of the core project, one could spin off a 3rd party project that wraps RobotJS around the WebDriver API. For ideas on that, to reduce work, one could base the wrapper skeleton around either the Appium project (currently node.js based, and follows WebDriver API to certain extent), or around any of the node.js WebDriver implementations - just take out the internal plumbing for what the UI automation does behind the scenes (for browser/mobile) and replace with code that invokes RobotJS. See https://github.com/daluu/autoitdriverserver or https://github.com/daluu/autopydriverserver as examples, which use the old Appium python implementation as the skeleton. |
@1j01 for clarification for readers to minimize searching, what modules exactly are we talking about here? Pointing out links to the details would be helpful. |
@daluu Generic RPC modules. |
Thanks for the link. Indeed, the access issue would apply to any desktop GUI automation tool, it's up to the user to decide how they want to deploy. Alternative options also could be to restrict access to the host running robot.js to only certain IP ranges, remote hosts, etc. including use of VPN, it at least limits the scope of access. |
like webdriver or other desktop automation spec?
The text was updated successfully, but these errors were encountered: