-
Notifications
You must be signed in to change notification settings - Fork 64
Description
What happened?
When using WebView2 as a PDF previewer in WinUI3, after upgrading the PC's Edge browser to the latest version 144.0.3719.82, it becomes impossible to navigate to specific pages of encrypted PDFs via the #page=index method. This function worked properly in version 140.0.3485.54.
In addition, specifying a WebView2 version is not feasible in WinUI3. Even when I copy the 140.0.3485.54 runtime environment locally, I cannot force the application to use this version by either setting environment variables via Environment.SetEnvironmentVariable or specifying the local runtime path through the CoreWebView2Environment.CreateWithOptionsAsync method.
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
144.0.3719.82
SDK Version
144.0.3719.82
Framework
WinUI3/WinAppSDK
Operating System
Windows 11
OS Version
26200.7623
Repro steps
- Create a WinUI3 application.
- Use WebView2 to open an encrypted PDF (with read-only access, no additional decryption required for reading).
- Append the hash tag #page=index when opening the PDF file.
- It is required to upgrade the Edge browser to the latest version 144.0.3719.82.
- Upgrade the operating system to the latest version 26200.7623.
- Run WinUI3 application
Repros in Edge Browser
Yes, issue can be reproduced in the corresponding Edge version
Regression
Regression in newer Runtime
Last working version (if regression)
140.0.3485.54