Problem with links height identification in IE 10.0.9200.16736 and later. Have anybody seen this?
Hi,
Several weeks ago the scripts that worked fine previously and were not changed started to consistently fail to click on some links on the web page.
There is no error reported to the test log because the link objects exist and are correctly identified by TestComplete with the only problem that their position (height) is reported to be below the actual link. Thus the click occurs below the actual link and does not trigger expected action.
This problem occurs not immediately but after some back and forth navigation through the site, so it is a bit problematic at the moment to provide exact steps to reproduce.
This problem occurs only with IE (Firefox and Chrome are OK) and I noted, that the problem does not happen on IE 10.0.9200.16686 but occurs on IE 10.0.9200.16736 and later, so I suspect that there was some change introduced in IE with the latest patches from MS.
The problem occurs with TC 9.31 and I did not checked it with TC 10 yet.
Considering that I don't have exact steps to reproduce at the moment, I am wondering if someone have seen something like this and can provide SmartBear's Support with the relevant steps?
To SmartBear Support: you are welcome to contact me directly if you think that I can help you somehow.
Several weeks ago the scripts that worked fine previously and were not changed started to consistently fail to click on some links on the web page.
There is no error reported to the test log because the link objects exist and are correctly identified by TestComplete with the only problem that their position (height) is reported to be below the actual link. Thus the click occurs below the actual link and does not trigger expected action.
This problem occurs not immediately but after some back and forth navigation through the site, so it is a bit problematic at the moment to provide exact steps to reproduce.
This problem occurs only with IE (Firefox and Chrome are OK) and I noted, that the problem does not happen on IE 10.0.9200.16686 but occurs on IE 10.0.9200.16736 and later, so I suspect that there was some change introduced in IE with the latest patches from MS.
The problem occurs with TC 9.31 and I did not checked it with TC 10 yet.
Considering that I don't have exact steps to reproduce at the moment, I am wondering if someone have seen something like this and can provide SmartBear's Support with the relevant steps?
To SmartBear Support: you are welcome to contact me directly if you think that I can help you somehow.