Elements detected, clicked in wrong location with Chrome

Test TestComplete
, , ,
1

Originally posted by batruong on April 21, 2026

Have a good day guys,

I am facing with the Elements can not detected exactly. It means like the title of this post.

Has this error been noted and fixed?

2

Originally posted by jkrolczy on April 21, 2026

This seems similar to a recent post:

Elements detected, clicked in wrong location with Chrome

3

Originally posted by jkrolczy on April 21, 2026

What version of TestComplete you using and Chrome version ?

4

Originally posted by jkrolczy on April 21, 2026

Well, my stuff was working until the Chrome updated.

Now my scripts are failing due to the latest TestComplete not supporting Chrome 147 :frowning:

I did open a support ticket.

5

Originally posted by batruong on April 22, 2026

Well, you can try by the other way , such as: clear chrome cache, or change to work with Edge

6

Originally posted by rrobinson on April 22, 2026

I see this also. Super glad that I see someone else seeing this issue in TC v15.79 also… I was losing my mind wondering what on earth is going on now… It REALLY SUX that it seems Edge and Chrome both - changing system settings to NOT leave open processes, instances of itself, tabs etc., open. TC really has issues with Edge and Chrome when it is not opened only by TC. If there are other Chrome processes running, then you load TC and try to run something - good luck getting the buttons to be found and clicked anymore. I get the same ‘highlight’ button showing way up and to the right from where that button is really. And this is in both v15,79 and the latest TC v15.81.7.7 and Chrome 147.

7

Originally posted by jkrolczy on April 29, 2026

I had the same issue and opened a case with SmartBear.

They do have a beta version being tested that help correct this issue for me.

I am assuming the new version will be out in May 2026?

8

Originally posted by detached310 on June 17, 2026

For us, the problem was fixed with the 15.82, released June 1st.