FitnesseForAppian- command to use scroll bar

Why would you need to scroll?

Why would you need to scroll?

I need to select the button which appears on the bottom of the page after searching a text.
Test fails as unable to locate the element and click on the button.

...and why would scrolling help that situation?

If fitnesse cannot locate the element, it's either not there or the identifier is wrong (or it doesn't have one). What does your script look like?

|populate field |field name |with value |value |
|wait for |5 |
|click on button |SEARCH |
|populate grid |Section name| column |Name |row |4|
|click on button |BUTTON NAME |

Initially I can see the button 'BUTTON NAME' is visible on the page. But when I search for a text and depending upon the number of results on the page, button name is pushed down and visible only when scrolling down the page.

In the application, I have so many sections with in the page which are visible only when scrolling down the page.

Does populating the grid affect the button's presence?

As I understand it, the fact that the page is scrolled to a particular position makes no difference to Fitnesse, as it is interacting with the page HTML/JS directly, rather than moving your cursor around or anything like that.

oh ok, then the problem should be actually in finding the element. Let me try and see again.
Thanks for your immediate response.

No problem - maybe you could use one of these:

| verify button | BUTTON_NAME or BUTTON_NAME[INDEX] | is present | Verify button with label is present
| verify button | BUTTON_NAME or BUTTON_NAME[INDEX] | is not present | Verify button with label is not present

Ah yes. Thanks

It is necessary to scroll. I have a test that runs fine, unless the screen resolution is low and the button is not visible. This just started since the screen was adjusted. The Site page buttons are now at the bottom and they obscure the button I am trying to press. The error is: ...Button... is not clickable at point (y, y). Other element would receive the click: ...This is the SiteHeader that contains page buttons... When I run the test locally with a high resolution, the button is visible and clicked. When I run on our remote build machine, the resolution is low and the button is clearly not visible. This is the only difference.

There are similar issues in Selenium WebDriver, which is the heart of FitNesse.