Working with Edge browser
Posted: Fri Oct 16, 2015 3:00 pm
Hi,
Using Ranorex 5.4.2 and Windows 10 with Edge browser.
When I use Spy against the Edge browser, it never jumps into the DOM and selects the element I tracked. It always goes to the WinApp object. It is very difficult to debug my code and get it working when this is not working.
I did notice something that is odd. My code starts the Edge browser. When I log into my app, the initially launched Edge browser opens another Edge app. So now I have the original winapp and its DOM and the second winapp and its DOM. In spy, the originally DOM is displayed in normal text and the second DOM is displayed in disabled color (light gray). If I try to track anything in the original DOM it will work. If I try to track in the second DOM, it will not. It will also not work in any other DOM spawned from the second winapp.
Did I configure something wrong, is it just not supported yet, or is this a bug?
Aracknid.
Using Ranorex 5.4.2 and Windows 10 with Edge browser.
When I use Spy against the Edge browser, it never jumps into the DOM and selects the element I tracked. It always goes to the WinApp object. It is very difficult to debug my code and get it working when this is not working.
I did notice something that is odd. My code starts the Edge browser. When I log into my app, the initially launched Edge browser opens another Edge app. So now I have the original winapp and its DOM and the second winapp and its DOM. In spy, the originally DOM is displayed in normal text and the second DOM is displayed in disabled color (light gray). If I try to track anything in the original DOM it will work. If I try to track in the second DOM, it will not. It will also not work in any other DOM spawned from the second winapp.
Did I configure something wrong, is it just not supported yet, or is this a bug?
Aracknid.