Hi,Since a few days, we've been noticing one of our TestExecute workers, running on v. 15.79.43.11 is detecting elements in the Chrome browser in the wrong location.A collegue has similar issues on their desktop, running TestComplete v15.80.1.7.Other TestExec workers and TestComplete instances running the same version (including the same version of the Chrome browser) do not experience this issue. Does anybody have an idea what might cause this?We've checked the obvious things as screen resolution and Windows zoom level. The issue doesn't occur with our regular AUT, only during interaction with Chrome.

The update for TC v 15.81.7.7 does NOT have a fix for this issue included. Just wanted to throw that out there in case someone else finds the object positions are fixed after installing the update.

Also experiencing the same issue now in Chrome 145.0.7632.117. Display scaling is at 100%, I am NOT using multiple browsers, and I can't even get past our login screen now which has worked for years because the elements are not being detected in the correct position.Unable to downgrade Chrome since it is organization managed, and updates get auto-installed. SmartBear once again fails to do beta testing to ensure compatibility of upcoming browsers.

It's relating to Windows Scaling, it needs to be set to 100%. See Testing With Various DPI Settings for more information.

I fixed the Problem with downgrading chrome to 143 from https://google-chrome.en.uptodown.com/windows/versionsUnfortunately the latest Supported Version for TC 15.80 according to docs is 138.If I create an issue as support case they tend to reply with saying which version is officially supported and suggest downgrading.But If a lot of people create cases asking for support of the latest chrome version, it may put pressure on SmartBear to release a fix soon.

We've been using TestComplete for several years now, and we often keep encountering problems after browser updates.Therefore, the underlying issue seems more significant to me:Smartbear doesn't test enough with pre-release versions (alpha, beta), leading to recurring problems with new browser versions.Furthermore, the versions officially supported by Smartbear are often more than six months old and thus unacceptable from a security standpoint.And also as mentioned before many companies have policies so that the browser will be updated "automatically" to avoid security problems.

Elements detected, clicked in wrong location with Chrome

26 Replies

rhu
Contributor
1 month ago
Hi we have same problems that Testcomplete clicks elements on wrong position, but had not time for deeper anaylse upt to now.
But I found an article that may could help
https://community.smartbear.com/discussions/testcomplete-questions/elements-detected-clicked-in-wrong-location-with-chrome/279220
MCH
Contributor
1 month ago
What helped me now was to remove Chrome and reinstall version 138 (latest officially supported version according to documentation).
It's strange that the issue occurred only couple weeks after updating to a newer version.
On other machines chrome still works flawless with version 143 or 145.
MCH
Contributor
1 month ago
We seem to have the same problem since today on one machine.
Not sure what changed because TC Version and Chrome Version are still the same as it was before today.
- rraghvani
  Champion Level 3
  1 month ago
  It's relating to Windows Scaling, it needs to be set to 100%.
  
  See Testing With Various DPI Settings for more information.
  - MCH
    Contributor
    1 month ago
    I forgot to mention, that scaling is already set to 100%.
    It was the first thing we checked.
    The behavior seems to appear only when we run Chrome from TestComplete via Browsers.Item[btChrome].Run().
    If I start Chrome manually every is fine.
    It also only happens on one machine. We are not able to reproduce it on other machines.

Forum Discussion

Elements detected, clicked in wrong location with Chrome

26 Replies

Recent Discussions

Application url change management

Delphi Mainmenu items is not clicked

TestComplete Chrome Host (32-bit) process not clearing up after running test

Related Content

TestComplete can't detect elements in Microsoft WebView2 window

Elements detected but is beyond the screen.

Screen elements in Chrome mobile view not detecting properly