-
Notifications
You must be signed in to change notification settings - Fork 55
[Problem/Bug]: Download fails on JS /w newpage #5196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
We are seeing the same behavior, and this is highly impactful to users. Can confirm: Simply installing 135.0.3179.54 causes the issue to manifest. In our application, one way we are using webview2 is to allow the user to access Sql Server Reporting Services. On clicking 'export to excel', the file download starts but never completes. |
@PhilipRieck @MichaeI-GH
|
20250410-0346-38.0891527.mp4This is how I tested it. Please check if there are any crashes here. Either visit "edge://crashes" from the webview or find dumps in the User data folder. For more details - https://github.com/MicrosoftEdge/WebView2Feedback/blob/main/diagnostics/crash.md |
As mentioned, we are using WinForms. If that's not what you're asking, please elaborate. The edge://crashes-page does not provide any crashes afterwards. To me it seems that the new tab opened by JS blocks the download. |
We are using the WPF control and seeing the same issue. What seems to happen is that a .tmp extension file is created in the Downloads directory but the process never completes and we are left with a gray window and the user never sees the downloads message. If you rename the .tmp file to the extension you were expecting (xlsx/pdf etc), the file is complete and useable. |
Hello, we have the same experience, we are also using WebView2 to host Reporting services reports; and now Export to Excel stopped working. WebView2 initialized from Microsoft.WebView2.FixedVersionRuntime.134.0.3124.93.x64.cab works, I was able to reproduce it by running your WebView2WindowsFormsBrowser sample (https://github.com/MicrosoftEdge/WebView2Samples) and navigating it to a public Reporting Services report at https://ssrs.fdot.gov/Reports/report/PDA%20Reports/Public%20Reports/ShortList Please have a look what has changed and fix it. |
Same issue for us on SDK 1.0.1150.38 and runtime 135.0.3179.54. |
Same issue for us |
Same issue than @janhavel1 here, WPF sdk 135 not work and 134 works |
Same issue for us |
We're using this in our software products and now have clients hitting this issue and complaining. This is going to start affecting a lot of people so an indication on when this may be fixed would be much appreciated. |
@ParadoxZero some information for all of us. What is happening, are you working on the issues and how to continue from now, because our clients complaining about this issue? |
Just wanted to add my voice. We have the same problem as @janhavel1 with report server. We host report viewer in a webview2 in WPF. We're starting to get more and more complaints from our clients as the new webview2 version rolls out... |
+1 The navigation to download pdf, xls, doc, .. all formats is broken. |
Folks, I managed to repro and understand the issue. Thanks a lot for all the help with diagnostics. Will update the thread once the fix has been merged. |
What happened?
Hi,
this occurred in an externally developed app of ours.
here's the examplecode I used:
(Here it's a .bin-File but in our Application it is a .doc file, both fail.)
Thanks!
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
135.0.3179.54
SDK Version
1.0.3230-prerelease
Framework
Winforms
Operating System
Windows 11
OS Version
22631.5039
Repro steps
Expected: The page opens & closes automatically + downloads the file in some visible way
Actual: The page opens but nothing else seems to happen
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
Regression in newer Runtime
Last working version (if regression)
134.0.3124.93
The text was updated successfully, but these errors were encountered: