Forum Discussion

3sV's avatar
3sV
New Contributor
8 hours ago

Elements detected but is beyond the screen.

Using Chrome Version 145.0.7632.117. We want to test with the latest version.
Using TestComplete Version: 15.76.5.7 x64

TLDR; version

browser.BrowserWindow.Maximize();

Maximize() makes my test fail because it thinks an object is off screen. Logging the browser position I see negative left and top results. The object is also outside the browser window.
Anyone else has this?

Long version

I only have this issue when I maximize the browser window.
Logging: Browser window position and size L,T,W,H = -8,-8,1910,911

Then my search box was not clickable, although I could see it on my screen.
Logging error: There was an attempt to perform an action at a point, which is beyond the screen. 

Logging the position and size of the search box reveled that it indeed was going of screen
Logging: Search box position and size L,T,W,H = 2600,336,186,31

Seems related to Elements detected, clicked in wrong location with Chrome | SmartBear Community but was requested to create new post.

My temp solution: setting a fixed browser window within the bounds of the window.

var browserWnd = Sys.Browser("chrome").BrowserWindow(0);
browserWnd.Restore();
browserWnd.Position(Left, Top, Width, Height);

1 Reply

  • Hassan_Ballan's avatar
    Hassan_Ballan
    Icon for Champion Level 3 rankChampion Level 3

    Based on what you’re describing and the similar reports in other threads, this looks more like an environment or display configuration issue than a pure supported Chrome version problem.

    A few things I would suggest checking:

    First, confirm the effective DPI using command line rather than relying only on the Windows UI. Open Command Prompt and run:

    wmic desktopmonitor get PixelsPerXLogicalInch,PixelsPerYLogicalInch

    If the value returned is 96, that equals 100% scaling. If you see higher numbers like 120 or 144, then scaling is above 100%, which can cause coordinate misalignment issues even if Display Settings appears correct.

    Second, test with only a single monitor connected and ensure the browser launches on the primary display. Additional or previously configured displays can affect coordinate calculations.

    Third, try clearing the TestComplete user settings by renaming the folder %LocalAppData%\SmartBear\TestComplete and then launching TestComplete again. This will reset local configuration and browser integration settings, which can sometimes resolve machine-specific coordinate issues.

    If this resolves your scenario, marking it as the solution helps future readers find it quickly.