MicrosoftEdge / MicrosoftEdge/WebView2Feedback
[Feature]: Requesting support for overriding/intercepting WebView2 PDF Viewer toolbar actions
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Describe the feature/enhancement you need
Hi Support Team,
We are currently developing a Windows Forms desktop application that utilizes the Microsoft WebView2 control to display internal PDF documents.
We need to implement a security requirement (or custom workflow) that intercepts the "Save As" button click on the built-in Chromium PDF viewer toolbar to trigger our own custom application dialog/logic instead of the standard Windows save dialog.
Because the built-in PDF viewer operates within an isolated chrome-extension:// origin, standard JavaScript DOM manipulation and event listeners are blocked by cross-origin security sandboxing. We are seeking your guidance on the recommended architectural approach for this.
Thank you in advance
Adrian
The scenario/use case where you would use this feature
When rendering a page what displays a PDF, I would like to overwrite the default functionality of the save button with my own functionality.
How important is this request to you?
Impactful. My app's user experience would be significantly compromised without it.
Suggested implementation
No response
What does your app do? Is there a pending deadline for this request?
No response
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 reviewing the WebView2 PDF viewer and its chrome-extension:// isolation described in the issue, focusing on whether toolbar actions can be intercepted or overridden. Done means identifying and documenting a supported architectural approach for replacing the built-in Save As workflow with application-specific logic.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100