We have an ESM script that's using Firefox 24.0, and one particular agent is having this issue: the browser object are recognized, but at the wrong location. So for example if we try to click the username field at a logon screen to activate the textbox, it will locate the object, but click way off the actual textbox, thus failing to activate it. This happens for all objects on screen.
If I use the object identifier, it will not find the objects at the correct location, but instead a bit off both from the X and Y axis. I can also navigate to a specific object via the tree, but when I click locate, the identifier will flash at the wrong place.
Has anyone seen this type of behavior before, and if so, what was the cause? I know I could/should open a ticket, but I will be out of office soon for a few weeks so I won't be able to follow up on it properly. That's why I thought I could ask for some general tips from here...
Answer by Yuriy L. ·
Forum, of course, is a great place. Hopefully other participants will bring their ideas. And it gives a chance to discuss how the problem can be looked at, while leaving actions up to the reader. You probably already know most, of what I am going to say, but... Here is my take.
1. You say "one particular agent is having this issue". What makes this machine different? Is it possible to make it identical to other machines? Cloning usually allows to make several machines behave the same way. If this is not possible, here are couple things to try:
1.1. Disable Firefox accelerated rendering, http://forums.mozillazine.org/viewtopic.php?t=1775755.
1.2. If the machine is running Windows 10, or Windows 8.1, or Windows Server 2016, or Windows Server 2012 R2, disabling High DPI scaling might help, https://support.microsoft.com/en-us/help/2900023/some-desktop-applications-may-appear-blurred-on-high-dpi-displays and https://appuals.com/disable-display-scaling-on-high-dpi-devices-in-windows-10/.
2. The coordinates you are getting are wrong. Coordinates are needed mostly for emulating mouse functionality. Try to avoid using mouse. For instance, instead of .Click you can put .SetFocus. Using Keyboard section of Monitoring Applications with Un-recognized Controls documentation page contains some approaches you may consider.
3. You can quit using controls altogether. In addition to recommendation in the already quoted Monitoring Applications with Un-recognized Controls documentation page, you can also use Screen object introduced in 12.5.3. Unfortunately, I cannot point you to any documentation page – we are a bit behind there. But Object Browser (View->Object Browser) contains signatures and brief descriptions of its methods and properties.
If you open a support ticket, we will, of course, help you with the approaches listed above and we may also try something else.