_webView2.CoreWebView2.WebResourceResponseReceived is not invoked
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start with the CoreWebView2Ready entry point shown in the report and review the WebResourceResponseReceived event setup. Compare behavior on Windows 10 and Windows Server 2016 using Microsoft.Web.WebView2 1.0.1418.22, with Fiddler confirming traffic. Done means identifying a reproducible cause for the missing event or documenting that the issue cannot be reproduced.
Written by the indexing model from the issue text.
Description
My application works fine on my laptop (Windows 10).
When the application runs on my dev VM (Windows Server 2016), the interaction with the Web server and rendering of web pages are all good, and the request and response messages exchanged with the Web server are captured by Fiddler; however, _webView2.CoreWebView2.WebResourceResponseReceived is not invoked.
The version of "Microsoft.Web.WebView2" package is "1.0.1418.22". The runtime version is the same on both machines:
private void CoreWebView2Ready(object sender, EventArgs e)
{
_webView2.CoreWebView2.WebResourceRequested += WebResourceRequested;
_webView2.CoreWebView2.WebResourceResponseReceived += ResponseReceived;
_webView2.CoreWebView2.ClientCertificateRequested += ClientCertificateRequested;
_webView2.CoreWebView2.Settings.AreHostObjectsAllowed = false;
_webView2.CoreWebView2.Settings.IsWebMessageEnabled = false;
_webView2.CoreWebView2.Settings.AreDefaultScriptDialogsEnabled = false;
_webView2.Source = new Uri(SsoEndpointUrl);
}
- Dominant language
- C++
- Stars
- 1k
- Forks
- 521
- Avg merge
- 13m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MicrosoftEdge/WebView2Samples
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 72/100
MicrosoftEdge/WebView2Samples#5 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
MicrosoftEdge/WebView2Samples#282 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MicrosoftEdge/WebView2Samples#277 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MicrosoftEdge/WebView2Samples#273 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
MicrosoftEdge/WebView2Samples#268 ·
All issues in MicrosoftEdge/WebView2Samples
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
EchoTools/nevr-runtime#116 ·
Maintainers usually reply within 1 day
-
code-quality libc++
Difficulty 1/5 Under an hour Newbie friendliness 82/100
llvm/llvm-project#229284 ·
Maintainers usually reply within 1 day
-
test-issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
llvm/offload-test-suite#1557 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
iOS: hidden scale bar invalidates its intrinsic content size on every layout pass of MLNMapViewOpen
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
maplibre/maplibre-native#4723 ·
Maintainers usually reply within 1 day