CEF technology limitation warning for Edge (Chromium) browser.

Technology specific object identification, supported applications, web technologies, and 3rd party controls.
ziasim
Posts: 48
Joined: Wed Dec 16, 2015 4:03 pm

CEF technology limitation warning for Edge (Chromium) browser.

Post by ziasim » Tue Jun 01, 2021 5:24 pm

Hi,

I am trying to automate user login on "login.salesforce.com" using Edge (Chromium based) browser. So, as I launch browser using the URL, Ranorex shows CEF technology limitation warning although it keeps identifying all UI elements of this page. But, when I ran test case which do login to this web site, it was unable to identify the login fields and hence test failed.

I read couple of similar posts where people asking similar question and the reply is that enable CEF debugging port with 8081. The questions are

- As ranorex guide said, "adding the following command line argument to the Run application action in a recording module"
-----As I mentioned, I am opening web page with login.salesforce.com URL, Does it mean I need to pass "–remote-debugging-port=8081" argument with Host.Local.OpenBrowser(varURL, varBrowserName, "", false, true, false, false, false, true) action?

- I also tried to run the compiled .exe with –remote-debugging-port=8081 argument but no use because it did not enable remote debugging port as well.

- I also uninstall/install Edge browser through instrumentation wizard but with result.

Ranorex version is 9.4.1 and Edge browser version is 91.0.864.37 (64-bit).

Any thoughts on how can I make sure to enable remote debugging port in above mentioned scenario?
Attachments
EdgeBrowser.rxsnp
(218.98 KiB) Downloaded 83 times
CEF warning.png
CEF warning.png (194.96 KiB) Viewed 1224 times

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 7221
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: CEF technology limitation warning for Edge (Chromium) browser.

Post by odklizec » Wed Jun 02, 2021 7:29 am

Hi,
ziasim wrote:
Tue Jun 01, 2021 5:24 pm
- As ranorex guide said, "adding the following command line argument to the Run application action in a recording module"
-----As I mentioned, I am opening web page with login.salesforce.com URL, Does it mean I need to pass "–remote-debugging-port=8081" argument with Host.Local.OpenBrowser(varURL, varBrowserName, "", false, true, false, false, false, true) action?
Yes, you must pass –remote-debugging-port=8081 to OpenBrowser action. This should do the trick with debugging port.
Pavel Kudrys
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

ziasim
Posts: 48
Joined: Wed Dec 16, 2015 4:03 pm

Re: CEF technology limitation warning for Edge (Chromium) browser.

Post by ziasim » Wed Jun 02, 2021 8:18 am

Hi odklizec,
you must pass –remote-debugging-port=8081 to OpenBrowser action
If do don't mind asking (not from coding background) how should I pass this argument to OpenBrowser action?

This is the line which opening browser in my code

var process ID = Host.Local.OpenBrowser(varURL, varBrowserName, "", false, true, false, false, false, true)

Should I pass this argument as browser parameter like

var process ID = Host.Local.OpenBrowser(varURL, varBrowserName, "–remote-debugging-port=8081", false, true, false, false, false, true)

I tried above method but it opened a browser tab with error "can't reach this page"

What is correct method to pass argument to OpenBrowser action??

Thanks in advance

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 7221
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: CEF technology limitation warning for Edge (Chromium) browser.

Post by odklizec » Wed Jun 02, 2021 8:50 am

Hi,

Try this:

Code: Select all

var process ID = Host.Local.OpenBrowser(varURL, varBrowserName, "-–remote-debugging-port=8081", false, true, false, false, false, true)
Pavel Kudrys
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

ziasim
Posts: 48
Joined: Wed Dec 16, 2015 4:03 pm

Re: CEF technology limitation warning for Edge (Chromium) browser.

Post by ziasim » Thu Jun 03, 2021 7:07 am

HI odklizec,

Using '--' did the trick.

Thanks for help.

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 7221
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: CEF technology limitation warning for Edge (Chromium) browser.

Post by odklizec » Thu Jun 03, 2021 7:31 am

Hi,

Nice to hear that! You are welcome.
Pavel Kudrys
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

Isaac
Posts: 11
Joined: Sun Feb 02, 2020 5:11 am
Location: South Africa
Contact:

Re: CEF technology limitation warning for Edge (Chromium) browser.

Post by Isaac » Thu Oct 28, 2021 1:46 pm

Hi odklizec,

In my case on edge(Chromium) browser when pressing the back button arrow it works but it continues to display the warning message :
"
UI elements in your CEF AUT can’t be identified because the remote debugging port isn’t enabled in your AUT or can’t be found. Make sure you’ve enabled it and set it to 8081.
Process: 'msedge' (pid 13100)
https://www.ranorex.com/help/v10.0/inte ... eshooting/
(This message is only shown once per report.)
".

How can I resolve the warning or what I'm missing?

Fergal
Certified Professional
Certified Professional
Posts: 403
Joined: Tue Feb 18, 2014 2:14 pm
Location: Co Louth, Ireland
Contact:

Re: CEF technology limitation warning for Edge (Chromium) browser.

Post by Fergal » Thu Oct 28, 2021 3:48 pm

Isaac wrote:
Thu Oct 28, 2021 1:46 pm
...In my case on edge(Chromium) browser when pressing the back button arrow it works but it continues to display the warning message :...
It might not be what you are looking for, but as a workaround you could use an Alt + Left Arrow key shortcut (Alt+Left) instead of clicking the back button on the browser. You are most probably just concerned with your app, and not the UI elements on the browser.

Isaac
Posts: 11
Joined: Sun Feb 02, 2020 5:11 am
Location: South Africa
Contact:

Re: CEF technology limitation warning for Edge (Chromium) browser.

Post by Isaac » Thu Oct 28, 2021 6:51 pm

Hi Fergal ,

I appreciate.
I'm aware of the control key shortcut. What concerns me is that with Chrome and Firefox I'm able to perform the same action without CETwarning. So, why does it occur with Edge Chromium, and how can the CET warning be removed or not generated from the report?

Fergal
Certified Professional
Certified Professional
Posts: 403
Joined: Tue Feb 18, 2014 2:14 pm
Location: Co Louth, Ireland
Contact:

Re: CEF technology limitation warning for Edge (Chromium) browser.

Post by Fergal » Fri Oct 29, 2021 9:41 am

Thanks for your reply Isaac, sorry but I don't know the answer to your question. Perhaps this link will help you: https://www.ranorex.com/help/latest/int ... lications/

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 7221
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: CEF technology limitation warning for Edge (Chromium) browser.

Post by odklizec » Fri Oct 29, 2021 9:45 am

Hi,

At first, please make sure the browser is started with –-remote-debugging-port parameter, as mentioned above. And at next, are you sure the page is identified as DOM, not as Form?
Pavel Kudrys
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

Isaac
Posts: 11
Joined: Sun Feb 02, 2020 5:11 am
Location: South Africa
Contact:

Re: CEF technology limitation warning for Edge (Chromium) browser.

Post by Isaac » Mon Nov 01, 2021 11:58 am

Here's the back buttom path:
"/form[@title=<tittleName>]//button[@accessiblename='Back']"
The web portal window-path:
"/dom[@domain=<urlName>]/body//div"

The thing is with Chrome and Firefox browsers, the back button click-action works fine and returns no CEF warning. So with EdgeChromiun return the CEF warning.

Any workaround or a way in which the warning can be disabled or filtered from the report by not using the Report level of a test suite structure method, but a method that disables CEF warning specifically?