MicrosoftEdge / MicrosoftEdge/WebView2Feedback
CustomScheme not working for documents
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
If I apply the following filter:
WebView2.CoreWebView2.AddWebResourceRequestedFilter($"app://*", CoreWebView2WebResourceContext.All);
Document requests (webview2.source) are not caught by the "WebView2.CoreWebView2.WebResourceRequested +=" listener.
However, requests for images within a file at app://* or XMLHttpRequest requests do arrive.
How is such a big failure possible that removes so much functionality?
:(
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with the WebView2.CoreWebView2.AddWebResourceRequestedFilter call and the WebView2.CoreWebView2.WebResourceRequested listener described in the issue. Reproduce a document request through webview2.source, then compare it with the image and XMLHttpRequest cases. Done means document requests for app://* are observed by the listener, or the limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100