Wrong/Unexpected Behaviour of Scroll Up/Down Robot Keyword

[rasihonurolgun]

Background:
We are trying to automate a testcase via robot framework via FlaUI library. We have a custom made GUI to control. Before, we were using TestStackWhite and with that library we were able to scroll up/down in the list and find the "element"/"row" we wanted to interact with.

Issue:
Now, we tried the same actions with FlaUI library however it appears that when the item we wanted to scroll to is not in the active view/not visible, it can't scroll to it and crashes.

• When the item is visible in the list that we wanted to check: Scroll up/down <XPath> keyword moves the mouse pointer to the correct visible item that we described with the Xpath.
• When the item is NOT visible in the list that we wanted to check: Scroll up/down <XPath> keyword moves the mouse pointer to the outside of the visible item list and it is not actually scrolling down or up. So, we are not able to select the item we want to interact with.

Here is the class definitions of our GUI and related screenshots from FlaUI inspect :

Used versions:
Robot framework flaui library version: 3.4.0
FlaUI library version: 4.0
Python version: 3.12

[noubar]

@rasihonurolgun
please try with uia2 also
and post here the errors you are getting for both uia2 and uia3
and post how you are using it with which arguments.

You can switch to uia2 as following in your robot test

Library    FlaUILibrary     uia=UIA2

Other than that it is not clear how do you want to scroll an element which is not there. If you are talking about scrollview it should not be a problem because this keyword sends a mouse action to the center of the given element as xpath

Normally scroll down in your case should be used as following

Scroll Down  /Window[@AutomationId='ShellUpdaterWindow']/Custom[AutomationId='UpdaterAppWindow']/Custom[AutomationId='ProceduresPanel']/Datagrid[AutomationId='lstProcedures']  <SomeInteger 10 or 100>

[rasihonurolgun]

@noubar Thanks for your response ! I was trying it without "focusing" or "clicking" on the GUI itself while I was trying to scroll up or down. Since I was debugging and trying the keywords, if GUI is not in the active window I was not able to see the functionality of the keyword.

Right now we were able to make it work and start to make our own custom keywords with that. Thanks a lot !