Forum Discussion
What happens if you call
Aliases.browser.pageQaInstanceArcadiaMode.panelMwindiv.frameMwinFrame.BatchUpdatetable.cellData1.selectUaDwritestatus.ClickItem('Append')
It appears that this is a standard drop down component... you don't need to map the individual drop down options, you should be able to call just a basic ClickItem call where the parameter of ClickItem is either the text identifier of the item to be selected or the numerical index.
The modal window slides down and the element is not visible on screen and the log information says, "There was an attempt to perform an action at point (47, 15) which is transparent or out of the window bounds."
- tristaanogre7 years agoEsteemed Contributor
Try, before you do the clickitem, call a "ScrollIntoView".. like so
Aliases.browser.pageQaInstanceArcadiaMode.panelMwindiv.frameMwinFrame.BatchUpdatetable.cellData1.selectUaDwritestatus.scrollIntoView(true); Aliases.browser.pageQaInstanceArcadiaMode.panelMwindiv.frameMwinFrame.BatchUpdatetable.cellData1.selectUaDwritestatus.ClickItem('Append');- amit_bansal7 years agoOccasional Contributor
Already tried that. It scrolls the element in to view but when clickitem is executed, it slides down. As I shared earlier, when element is visible on screen and I tried highlighting, it slides down and the property visible on screen turns False.
- tristaanogre7 years agoEsteemed Contributor
So... it's the actual modal window the scrolls and not the drop down control?
Then call "scrollIntoView" on the modal, not the drop down control... make sure that the modal is fully on screen properly.