"No valid low-level click position found" means that the DOM element which is identified by the locator (parameter of BrowserClick()) is somehow not visible and therefore Silk Performer does not find a way to click on it. Silk Performer tries sending a JavaScript event (as in previous versions of Silk Performer) as fallback (High-level fallback used) but it seems that it does not work. You could give it a try and enable "Legacy Input Mode" in the Profile Settings dialog which restores the "old" JavaScript user input simulation (which is less exact but works better in some cases). Background Info: In newer versions of Silk Performer native user input is simulated which is more exact and usually works better in most cases out of the box. For example: In the past you had to replace BrowserSetText() by BrowserTypeKeys() to get a working script for some web applications. Now it does BrowserTypeKeys() under the hood automatically. You can turn off this new kind of user input simulation as described above. To "Scrolling functionality failed": Before each script action in the browser Silk Performer scrolls to the specified DOM element so that it is visible in screenshots. I cannot say why this is failing in your case. Maybe you should try another locator. There exist some tricky DOM elements which are hard to scroll to automatically. Are you sure this DOM element is visible? Just check and use Locator Spy to find out more about the DOM in the problematic web page.
↧