MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Add Site Origin and Frame Origin to WebResourceRequested event.
@Lakshmisha-KS is already working on this.
Since Feb 12, 2025.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
The current WebResourceRequested event does not provide a way to identify which page the request originated from.
A basic approach could be to use the current WebView2.Source to get the current page url, or using the NavigationStarting Event. However, due to the way pages are loaded and unloaded by WebView2/Chromium, there is an overlap during the transition from one page to the other where either the new or old page can be sending the requests.
Another approach might be to inspect the referer or origin headers, but not all requests include said header.
As such, we are looking for the Site Origin (and optionally Frame Origin) properties to be added to:
- WebResourceRequested event
- Chromium DevTools protocol's Fetch.requestPaused event
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.
Assessment
This issue has not been assessed yet.