WebView2 support does not work

I've been looking into this, and learning about WebView2. I have a simple C# WebView2 forms application that displays a web site.

C# WebView2 form application

The Object Browser shows the following

Standard UI controls exposed

Enabling MSAA (TC -> Project Settings), exposes the controls of the application

Application controls exposed

Enabling UI Automation (TC -> Project Settings), exposes even more of the application

More controls exposed of the application

and also WebView2, including the UI controls within

WebView2 and all UI controls with

For this to work correctly, the appropriate flag settings needs to be enabled for WebView2 control within the application.

Using TC version

If you're using Selenium WebDriver, then you can use the following command (I haven't tested this)

var environment = await CoreWebView2Environment.CreateAsync(null, null, new CoreWebView2EnvironmentOptions("--remote-debugging-port=9222"));
await webView.EnsureCoreWebView2Async(environment);

I hope this helps, and gives you a starting point.

That switch is only applicable to the Chromium browser, i.e. Edge. Are you using the appropriate version that supports WebView2, https://support.smartbear.com/testcomplete/docs/general-info/whats-new.html?sbsearch=webview2 

Its the second Testcomplete version (15.70) that states either Web View 2 is supported or there were improvements made to Web View 2 support. Still there is zero article in the Testcomplete documentation pages that tells the user how to get this to work.

Can someone on here tell how to get this to work?

I have an embedded WebView2 components within our desktop application (.NET/Winform) - I've found that i couldn't expose the contents of the component inside/under the WebView2 parent object.

I have ensure the settings as you suggested in the post above are used in my T.C project setting

Sharing some findings that might help others evaluating WebView2 with TestComplete:

🔎 Current Observations

• While TestComplete versions since 15.69 mention WebView2 support, there’s still no official documentation on how to achieve full object recognition inside the control.
• Based on community reports, DOM-level mapping via XPath/CSS selectors (as in typical web testing) is still not working.
• UI Automation can expose some UI elements within WebView2, but not actual web content in many setups.

🛠️ Technical Option to Explore

For teams able to modify the application, you might consider enabling remote debugging on the WebView2 control. Example (C#):

var env = await CoreWebView2Environment.CreateAsync(
    null, null, new CoreWebView2EnvironmentOptions("--remote-debugging-port=9222"));
await webView.EnsureCoreWebView2Async(env);

Then attach a Selenium session:

from selenium import webdriver
from selenium.webdriver.chrome.options import Options

opts = Options()
opts.add_experimental_option("debuggerAddress", "localhost:9222")
driver = webdriver.Chrome(options=opts)

This can provide DOM access to WebView2 content, similar to how Chrome DevTools works.

🔧 Notes

• This approach may not work for all applications — especially if the WebView2 environment can't be configured to allow remote debugging.
• It requires coordination with development to set up correctly.
• A few users in the community have partially validated this, but no complete end-to-end examples are available yet.

Hopefully, this gives others a direction to investigate further while waiting for clearer support from SmartBear.

🤖 AI-assisted response
👍 Found it helpful? Click Like
✅ Issue resolved? Click Mark as Solution