ContributionsMost RecentMost LikesSolutionsRe: VisibleOnScreen is True when web object is not clickable Thanks for this information, it is very helpful! I believe I can use this in other situations which are fragile to make them more robust, such as a fixed banner bar which overlaps underlying links and ScrollIntoView cannot be relied on. I appreciate the detail, I should be able implement this based on your steps. Many thanks! Re: VisibleOnScreen is True when web object is not clickable The objects are indeed Enabled, Visible and VisibleOnScreen, although only partially and cannot accept a focus when I manually do a roll-over. I was going by the TestComplete Documentation, which indicates in the Remarks it could be used for visible controls that accept mouse clicks: Remarks •The VisibleOnScreen property returns true, if a control or its part is on screen and can accept mouse clicks. For example, focused controls whose opacity is set to 0 are absolutely transparent (that is, invisible), but their VisibleOnScreen property will return true. •The VisibleOnScreen property is always false for disabled Silverlight controls. After more investigation, this appears to only happen in Chrome and not FireFox, so I am wondering if perhaps it's an issue with Chrome or that TC extension? Thanks for trying to help me out, I am puzzled and haven't found a work-around yet for my web app. VisibleOnScreen is True when web object is not clickable I am using TestComplete 12, and some of my web tests are failing now due to the VisibleOnScreen property value being True when the web object (Panel or TextNode) is partially visible but not clickable and not able to set focus. This is happening in both Chrome and Firefox browsers, latest versions. Is this a known issue to be fixed? Previously, I could safely check VisibleOnScreen to determine if the web object could be clicked. Test Complete Pause Function Does the Test Complete Pause function allow input/output interaction with the application under test GUI while in Pause? The documentation says it enters Debug-mode, but I'm wondering if this functionn could be used to stop the script and allow a user to take over testing for awhile, then resume the automated script once they have done some actions. Is that possible? Solved