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.

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.

Furthermore, the versions officially supported by Smartbear are often more than six months old and thus unacceptable from a security standpoint.We also see this as a big issue that support for newer versions is becoming slower and slower.It started with Firefox but this is another topic. New Chrome versions were usually working without TestComplete Updates or were patched pretty soon after release. We never really had to check which version was mentioned in the docs.

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.

Elements detected, clicked in wrong location with Chrome

23 Replies

scottroutesmart
Contributor
9 days ago
Issue still occurs on Chrome 145.0.7632.160 too, which I just installed.
scottroutesmart
Contributor
9 days ago
As a temporary workaround downgrading to Chrome 1.44 seems to work, but for many of us I know that updates are company managed so this is very temporary. (This does show an incompatibility issue between TC and Chrome 1.45 imo.)

Here is a link to get older Chrome versions for reference:
chrome-versions/versions.json at main · ulixee/chrome-versions · GitHub
MarcusBe
Contributor
4 days ago
I assume this issue is not going to be resolved in the near future, will try to talk to IT if its possible to downgrade
- rhu
  Contributor
  4 days ago
  We tried and downgraded chrome but it updated although we created a group policy that it should not.
  So if you know how to disable the chrome update it would be helpful if you coud post it here.
  - MarcusBe
    Contributor
    4 days ago
    Not yet sure if this works im in the process of trying it out
    
    Method 1: Disable Services (Recommended)
    Press Win + R, type services.msc, and hit Enter.
    Locate Google Update Service (gupdate) and Google Update Service (gupdatem).
    Double-click each service, change the Startup type to Disabled, and click Apply.
    Switch to the "Recovery" tab and set "First failure" and "Second failure" to Take No Action.
    
    Method 2: Rename the Update Folder
    Navigate to C:\Program Files (x86)\Google\
    Rename the Update folder to something else (e.g., Update.bak).

Forum Discussion

Elements detected, clicked in wrong location with Chrome

23 Replies

Recent Discussions

Access Form opend with a menuitem

Can we set sheet name in excel as active using python script

Unable to capture objects inside iFrames in Power App using TestComplete

Related Content

TestComplete can't detect elements in Microsoft WebView2 window

Elements detected but is beyond the screen.

Trouble Recording Tests for WPF WebView2 Application – Entire Window Detected Instead of UI Elements