Hi All,
We recently added a web-based element that opens within our non-web application. Initially, we were using the standard .NET web controls based on IE. At that time, I was able to identify objects normally, with no problems.
However, we recently changed to using Chrome web controls using the EO.WebBrowser for .NET. Since we made this change, I am completely unable to identify objects on the web page.
If I open the web page directly in Chrome, I can identify objects with no problem, but from within the app, I get nothing.
- I verified that the Chrome extension is installed and active.
- I tried using the GDI Capture Settings.
- When I spy the web page, it identifies the whole thing as "Element 'Chrome_WidgetWin_0".
Does anyone have any experience using this web control? I have been unable to find any useful information on the web.
EO.WebBrowser for .NET
Re: EO.WebBrowser for .NET
Hi,
Have you checked this User Guide chapter?...
https://www.ranorex.com/help/latest/int ... lications/
I think your only hope is to (somehow) enable remote debugging in your app, as described in the user guide.
The reason why tracking worked in embedded IE is, that IE does not require Ranorex plugin for element recognition, while Chrome does. And at second, Ranorex currently supports only the CEF browsers, mentioned in the above link. In other words, you may be out of luck, even with enabled remote debugging port.
Have you checked this User Guide chapter?...
https://www.ranorex.com/help/latest/int ... lications/
I think your only hope is to (somehow) enable remote debugging in your app, as described in the user guide.
The reason why tracking worked in embedded IE is, that IE does not require Ranorex plugin for element recognition, while Chrome does. And at second, Ranorex currently supports only the CEF browsers, mentioned in the above link. In other words, you may be out of luck, even with enabled remote debugging port.
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration