Edge issue: MoveTo not going to correct place
Posted: Fri Jul 31, 2015 2:28 pm
Hi,
[NOTE: I edited this. Please see Edit info at the end]
Using Release Windows 10 Pro and Ranorex 5.4. Scripts are coded in VS 2012 using VB.NET and Ranorex API, not the Studio.
When running my scripts, I have found that Windows 10 and/or Edge is sluggish and trying to simply "click" on web elements doesn't always work when the script initially runs. So I added some code to my framework to "moveto" the element over the time span of 1 second, so I can visually see where the mouse is going to click (so I had assumed). I've noticed that often it does not move to the correct location. It moves close to the correct location. It looks like it is offset by the amount that the Edge window is offset from the top-left corner of windows, but I cannot confirm this is exactly the case. Obviously, Edge is not maximized at this point. But oddly enough, when I do the "click" it does jump it to the right spot, and most of the time the click works.
I also have issues where "moveto" doesn't move to the correct location when Edge is maximized, and it looks like it is off by only the height. So it looks like it is moving to a location about 20 pixels (just a guess) above where it should be moving to. Again, after this move, the click jumps to the right spot and the click sometimes works.
I believe by adding the "moveto" code to my framework, I slowed down the script which gives Edge/Windows more time, and is why it mostly works. If I remove the "moveto", most clicks get missed.
[Edit] To clarify, this only seems to happen when I try to act on the first element in the DOM. So in my case, I launch Edge and get my log in screen for my AUT. I enter user name and password. When I try to click the logon button, it fails. So I added moveto, which moves to the wrong location, but then the click works. This in turn will launch another DOM which is the AUT main application. In this DOM, the first click has the same issue. IT will move to the wrong location and the click will work. Once I have done the first moveto/click, from this point on it seems to work, that is all the moveto commands seem to go to the correct place and all the clicks work. Since I'm no longer using the first DOM (log in screen), I cannot confirm that further clicks in this screen would work. Sometimes in the Main AUT, other DOMs will popup as features are triggered. I have not noticed if the first moveto/click in here also has the same issue.
Is anyone else experiencing this?
Aracknid
[NOTE: I edited this. Please see Edit info at the end]
Using Release Windows 10 Pro and Ranorex 5.4. Scripts are coded in VS 2012 using VB.NET and Ranorex API, not the Studio.
When running my scripts, I have found that Windows 10 and/or Edge is sluggish and trying to simply "click" on web elements doesn't always work when the script initially runs. So I added some code to my framework to "moveto" the element over the time span of 1 second, so I can visually see where the mouse is going to click (so I had assumed). I've noticed that often it does not move to the correct location. It moves close to the correct location. It looks like it is offset by the amount that the Edge window is offset from the top-left corner of windows, but I cannot confirm this is exactly the case. Obviously, Edge is not maximized at this point. But oddly enough, when I do the "click" it does jump it to the right spot, and most of the time the click works.
I also have issues where "moveto" doesn't move to the correct location when Edge is maximized, and it looks like it is off by only the height. So it looks like it is moving to a location about 20 pixels (just a guess) above where it should be moving to. Again, after this move, the click jumps to the right spot and the click sometimes works.
I believe by adding the "moveto" code to my framework, I slowed down the script which gives Edge/Windows more time, and is why it mostly works. If I remove the "moveto", most clicks get missed.
[Edit] To clarify, this only seems to happen when I try to act on the first element in the DOM. So in my case, I launch Edge and get my log in screen for my AUT. I enter user name and password. When I try to click the logon button, it fails. So I added moveto, which moves to the wrong location, but then the click works. This in turn will launch another DOM which is the AUT main application. In this DOM, the first click has the same issue. IT will move to the wrong location and the click will work. Once I have done the first moveto/click, from this point on it seems to work, that is all the moveto commands seem to go to the correct place and all the clicks work. Since I'm no longer using the first DOM (log in screen), I cannot confirm that further clicks in this screen would work. Sometimes in the Main AUT, other DOMs will popup as features are triggered. I have not noticed if the first moveto/click in here also has the same issue.
Is anyone else experiencing this?
Aracknid