MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Feature]: Fire WebResourceResponseReceived Event for frames

Open
#4,529 0 comments 0 reactions 1 assignee View on GitHub

@Lakshmisha-KS is already working on this.

Since Feb 12, 2025.

feature request
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

Describe the feature/enhancement you need

The WebResourceResponseReceived Event is not called for frames. Please fire it also for frames.

The scenario/use case where you would use this feature

In my app i save PDF files for further processing.
The event is not fired when a PDF is inside a frame so i cannot get PDFs inside frames.

Oh, i just figured out i cannot use it anyway because GetResponseAsync does not return the PDF... it returns HTML like this:

Anyway... please add support for frames. For me it's an error when this event does not return the raw servers response but instead presents a custom html with useless information... i hope that it will be fixed

How important is this request to you?

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

Suggested implementation

Call the WebResourceResponseReceived Event also for frames.
Maybe add a property in CoreWebView2WebResourceResponseReceivedEventArgs to indicate whether the request is from a frame.
Or add a new FrameWebResourceResponseReceived Event

I suggest to also make WebResourceRequested usable for frames.

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

I will keep using CEF/CefGlue until there is a solution for this issue

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.