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

Unable to interact with elements on the second tab #100

Open
KhaledFarhat opened this issue May 22, 2019 · 1 comment
Open

Unable to interact with elements on the second tab #100

KhaledFarhat opened this issue May 22, 2019 · 1 comment

Comments

@KhaledFarhat
Copy link

I am using Winium with Java to automate a Visual FoxPro desktop application, it has been working well for the most part until i started interacting with multi tab forms (inner windows).

Winium is able to interact with element on the first tab of a specific pop-up form or window, but when i do actions that would cause the second tab to be opened i am unable to perform actions on the elements there, Winium just stays there doing nothing, it does not error out until i manually close that window, so it tries to locate the element but it never actually is able to and just stays there doing nothing.

The elements are there when the application is inspected using the Inspect.exe app on windows, here is a sample of what it looks like on the inspection tool:
image
so by default i am able to perform actions on all the subelements of the "list" tab as its my main, the application has an Add button on that tab which result in the second tab being open "info", after that takes place i am unable to interact with any of the child elements of the "info" tab using the regular Winium commands.

Another approach was also tested to use the Actions library to navigate to that location of the element and trying to click on it, the mouse moves there and the click action is executed from code perspective but the click never actually takes place. please note that it was verified that both tabs relate to the same WindowHandle.

Any ideas or possible workarounds for this would be highly appreciated.

@nananand7
Copy link

Info tab should have the parent element. For example, info tab may have n number of chil elements, all these childs are covered under single parent - AutomationId of lnfo tab. Use the parent tlement to find the childs.

Eg: @driver.findElement(id:'infoParent').findElement(id:child)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants