[Feature]: Send requests and read responses programmatically and skip rendering

[viktoriya-lysenko]

Describe the feature/enhancement you need

We use WebView2 both in UI and non-UI mode. It's critical for some customers to use WebView2 for both UI and non-UI otherwise authentication cannot work properly. We send very large requests and responses in non-UI mode to get various financial data from data providers we show not in browser, but in Excel. Some of these responses cannot be rendered by WebView2 UI (result in COREWEBVIEW2_PROCESS_FAILED_KIND_RENDER_PROCESS_EXITED). We would like to be able to get body of a response even if it cannot be rendered and we would like to skip rendering completely as it would greatly improve performance and allow workaround this bug.
Corresponding SR#2501100010000531

The scenario/use case where you would use this feature

User creates a request using either special querylanguage (MDX) or data from Excel worksheet and it gets sent to data provider using NavigateWithWebResourceRequest and then our add-in reads the response programmatically, processes it and uses Excel APIs to show data from response on Excel worksheet.

How important is this request to you?

Impactful. My app's user experience would be significantly compromised without it.

Suggested implementation

Please add a function to CoreWebView2WebResourceRequest similar to CreateWebResourceRequest that would create a request that should be sent without rendering and showing the response on UI (e. g. CreateWebResourceNonUIRequest) OR add a function to CoreWebView2 similar to NavigateWithWebResourceRequest (e. g. NavigateWithNonUIWebResourceRequest) that would send a request that should not be rendered and showed on UI.

What does your app do? Is there a pending deadline for this request?

Our app is actually an add-in to the MS Office with Excel being used most heavily. It is used by thousands of large companies who have hundreds and sometimes thousands of users. We mostly handle financial data and analytics. Performance and being able to handle large amounts of data is greatly important to our customers. There is no pending deadline, but it would be great if we could include it in our September release (so if it's implemented by mid-August it would be ideal).

[Badhri]

Hi @viktoriya-lysenko ,

We would like to understand more on why and for what kind of response you receive COREWEBVIEW2_PROCESS_FAILED_KIND_RENDER_PROCESS_EXITED ?
Is it consistently happening ?
If yes, can this be mocked to provide a sample repro app ?
You can start with tweaking our sample app from here

[viktoriya-lysenko]

It's a large XML with complex structure. It's happening very consistently for a response that contains financial data of a large customer, but I obviously cannot provide that XML. I am working with an engineer who was assigned the SR I mentioned above to reproduce the issue without customer data.