Hi!
This is to ensure drop-in-replicability with WinAppDriver.
What exactly I mean:
WinAppDriver returns the current element when searching for itself on its instance.
Similarly, WinAppDriver returns the current element when searching for it on its representing session, e.g. when you have a window and its according session and you want to find the window as an element on the session, this works with WinAppDriver.
Unfortunately, the above cases do not work with FlaUI.WebDriver, because it seems to only search the children of the current element, not taking the element itself into account.
In any case, FlaUI.WebDriver responds with a 404 error:
"No element found with selector 'css selector' and value '#e0e08298\\-a77a\\-4cd7\\-a5a4\\-cc67d4780acb'"
Used versions:
- FlaUI.WebDriver v0.3.3
- Selenium.WebDriver v4.29.0
- The client code is wrapped on our side in .NET Standard 2.0 code.
Would be great to have this feature to improve migration from WinAppDriver!
Hi!
This is to ensure drop-in-replicability with WinAppDriver.
What exactly I mean:
WinAppDriver returns the current element when searching for itself on its instance.
Similarly, WinAppDriver returns the current element when searching for it on its representing session, e.g. when you have a window and its according session and you want to find the window as an element on the session, this works with WinAppDriver.
Unfortunately, the above cases do not work with FlaUI.WebDriver, because it seems to only search the children of the current element, not taking the element itself into account.
In any case, FlaUI.WebDriver responds with a 404 error:
Used versions:
Would be great to have this feature to improve migration from WinAppDriver!