Forum Discussion
ArtemS
Alumni
14 years agoHello,
Most of internal dialogs and notifications in Internet Explorer versions 8 and 9 (and many other Microsoft products) are implemented via OS-drawn DirectUIHWND controls. The exact version of the DirectUIHWND mark-up and its rendering engine API depends on the OS, and it is not documented by Microsoft. Due to this, TestComplete (as well as other automation tools) may have recognition issues when dealing with the DirectUIHWND controls. Sometimes, these issues can be dodged by exposing the DirectUIHWND classes ("DirectUIHWND", "#32770" or whatever else) via the Active Accessibility engine or by simulating coordinate clicks. Yet, these workarounds are not always consistent.
I have reproduced your problem on a test machine. In your case (Windows 7 + IE 8), the solution is to add "#32770" WndClass to the list of accepted windows in Project Properties - MSAA Options dialog (for IE9, exposed WndClass should be "DirectUIHWND").
Hope this helps.
Artem
Most of internal dialogs and notifications in Internet Explorer versions 8 and 9 (and many other Microsoft products) are implemented via OS-drawn DirectUIHWND controls. The exact version of the DirectUIHWND mark-up and its rendering engine API depends on the OS, and it is not documented by Microsoft. Due to this, TestComplete (as well as other automation tools) may have recognition issues when dealing with the DirectUIHWND controls. Sometimes, these issues can be dodged by exposing the DirectUIHWND classes ("DirectUIHWND", "#32770" or whatever else) via the Active Accessibility engine or by simulating coordinate clicks. Yet, these workarounds are not always consistent.
I have reproduced your problem on a test machine. In your case (Windows 7 + IE 8), the solution is to add "#32770" WndClass to the list of accepted windows in Project Properties - MSAA Options dialog (for IE9, exposed WndClass should be "DirectUIHWND").
Hope this helps.
Artem