MicrosoftEdge / MicrosoftEdge/WebView2Feedback
[Problem/Bug]: Window.print doesn't work on fixed runtime unless ALL APPLICATION PACKAGES permissions set
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
What happened?
The documentation for Webview2 says the following:
On Windows 10 devices, starting with Fixed Version 120, developers of unpackaged Win32 applications using Fixed Version are required to run the following commands, for Fixed Version to continue to work. This is due to a security improvement in v120 to run the Renderer process inside the App Container. This change doesn't affect Windows 11 devices, the older runtime, or packaged apps.
However, window.print shows up empty on Windows 11 if these permissions are not set.
Importance
Low. My app is not very affected, or this only affects development.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
128.0.2739.63
SDK Version
1.0.2739.15
Framework
WPF
Operating System
Windows 11
OS Version
22631.4037
Repro steps
-
Add a fixed webview to WPF application on windows 11 without setting the permissions
-
try to print any page
-
print preview does not load and the print doesn't work if fixed runtime is used
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
Regression in newer Runtime
Last working version (if regression)
123.x.x.x
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 WPF fixed-runtime case on Windows 11 22631.4037 with WebView2 128.0.2739.63, using the listed steps for window.print and print preview. Compare behavior with and without the ALL APPLICATION PACKAGES permissions and against the corresponding Edge version; done means the Windows 11 scope of the failure is confirmed and its expected behavior is established.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100