-
Notifications
You must be signed in to change notification settings - Fork 169
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
JSRuntime issue: after JS-invoking print
, the application becomes very broken
#408
Comments
actually, I think I confused myself: this bug exists in 0.5.50 as well, however if you use Ctrl+P to print page, there are no ill side effects. view:
code-behind:
I also tried the suggestion here: https://stackoverflow.com/questions/67206330/window-print-in-blazor-wasm where the print method is moved into a custom JS function (not sure why that would matter, but I tried it, anyway), and the problem persisted. I also-also tried making I am able to again, using Ctrl+P to print works fine; using
|
print
, the application becomes very broken
I just tried changing the button to instead be:
and that works, without any ill side-effects! so weird... |
Hmm yes weird indeed! I'm surprised that one works and not the other! |
I've attempted to create a minimum project which will show the issue, however I'm unable to test it because I'm getting that "can't reach this page" issue I mentioned in the other issue (#416) maybe there's some environment difference, though, and it'll work for you?? I've posted it here: https://github.com/BenMakesGames/MBBPrintBug |
@Eilon I have a minimum project demonstrating the issue (now working, thanks to your hint about explicitly including WebView2), here: https://github.com/BenMakesGames/MBBPrintBug I've added some notes on the print page about how to reproduce and see the issue. (seen here: https://github.com/BenMakesGames/MBBPrintBug/blob/main/PrintBug/Pages/Print.razor ) |
after calling
JSRuntime.InvokeVoidAsync("print")
,<a href>
s stopped working (clicking them had no effect).rolling back to 0.5.50 resolved the issue.
The text was updated successfully, but these errors were encountered: