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
WebDriver API for FlaUI #227
Comments
I would love to see something like this. I have looked into something like this before because I was wrapping selenium, the problem I ran into is adapting the API for AutomationElement to the elements returned by Selenium. Elements in the DOM have many attributes that don't map very well to the properties on AutomationElement. Of course writing the translation layer was trivial but I had to constantly keep checking what property mapped to what attribute in the browser. The experience felt less than ideal. |
Nice to see interest from others. I would think the translation part and constantly checking about the mapping is only for initial implementation and when there are new changes around AutomationElement from FlaUI or WebElement in WebDriver spec in future versions. The latter of which I assume doesn't change all that often, at least for WebDriver spec, FlaUI I'm not as aware for frequency of element object spec change. If the assumption is true, this isn't that bad to do for a project/implementation. Do once, and minimal maintenance thereafter. |
I wasn't aware a similar issue was opened for this topic: #50, I guess either one can be marked duplicate then. |
well, maybe not, if the other issue won't be following Webdriver API spec. |
Now refer to #594 |
This is just a suggestion, so that FlaUI could be like WinAppDriver or Winium. Could be a 3rd party project to provide the WebDriver API support to FlaUI.
Implementation could be to base the WebDriver API wrapper around how WinAppDriver or Winium does it, or to base off something like https://github.com/jimevans/strontium.
I'd consider contributing to this if/when I have some time.
The text was updated successfully, but these errors were encountered: