Progress® Telerik® Test Studio® Feedback Portal
Back to Feed
Request a Feature Report a Bug
Completed
Last Updated: 03 Nov 2015 07:47 by ADMIN
Ewin
Created on: 07 Apr 2015 17:39
Type: Feature Request
1
related to this feedback item drop and drop moves window
When drag and dropping an element, the internet explorer window goes from one monitor to the other.  It's similar to how the original feedback item states that the window was resizing.  

http://screencast.com/t/WXz1j4jUo

http://feedback.telerik.com/Project/161/Feedback/Details/153087-drag-and-drop-step-resizes-the-browser
3 comments
ADMIN
Daniel Djambov
Posted on: 08 Apr 2015 13:39 
Telerik: this is what I tried to explan - when the test was recorded, the browser was on your left monitor and drag and drop step has coordinates relative to top left of the left screen on the desktop, so during execution, no matter where the browser is positioned in the meanwhile, it will always move the browser to its initial state at the left montor, where the drag and drop step was recorded initially. Hope I was able to explain it correctly.
Ewin
Posted on: 08 Apr 2015 13:02 
OK, that makes sense.  So in that screencast, you may have noticed that my internet explorer window was on the right monitor then was moved to my left monitor.  

So I tried it with the left monitor and I assumed it would move to my right monitor but it stayed on the left monitor.
ADMIN
Daniel Djambov
Posted on: 08 Apr 2015 07:42 
Telerik: this is actually the expected behavior as per our current implementation - drag and drop operations are recorded with the coordinates of the browser related to the desktop at the time of the Recording - so when they are executed and browser is at a different position, we set it to the original position where it was when step was recorded, to ensure proper initial condition. We can consider taking the drag and drop position of the element from the current browser position instead, but if the size of the browser is changed and drag or drop points are not visible/in scope this will fail the operation, so it is not bullet proof. What is the inconvenience caused by the current behavior, so we can consider some changes there? Our presumption is that when executing automation tests, the environment is dedicated for this execution and no other actions are appropriate at that time.
Create an account Log In
View
Type
Status