MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Unable to capture continuous location.href through AddWebResourceRequestedFilter
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Description
Unable to capture continuous location.href through AddWebResourceRequestedFilter.
Version
SDK: 1.0.1774.30
Runtime: 113.0.1774.42
Framework: WinForms
OS: Win11 10.0.22621.1776
Repro Steps
- (In C#)
loginWebView.CoreWebView2.AddWebResourceRequestedFilter("callnative:*", CoreWebView2WebResourceContext.All);
loginWebView.CoreWebView2.WebResourceRequested += CoreWebView2_WebResourceRequested;
- (In JavaScript)
location.href = "callnative://command?arg1=value1";
location.href = "next.html";
CoreWebView2_WebResourceRequestedunable to capture thecallnative://command?arg1=value1.
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 by reproducing the C# WinForms setup using AddWebResourceRequestedFilter and the WebResourceRequested handler, then run the JavaScript sequence that assigns location.href twice. Compare the handler's events with the reported callnative:// request and next.html navigation. Done means the behavior is explained and the issue has a confirmed fix path or documented limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, javascript
- Domain
- desktop, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100