JSRuntime issue: after JS-invoking `print`, the application becomes very broken
See original GitHub issueafter calling JSRuntime.InvokeVoidAsync("print"), <a href>s stopped working (clicking them had no effect).
rolling back to 0.5.50 resolved the issue.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Issues · dotnet/MobileBlazorBindings
How to solve "Invalid Emulator component" issue in Mobile Blazor Bindings ... JSRuntime issue: after JS-invoking print , the application becomes very broken....
Read more >How to inject in blazor code behind .razor.cs file? ...
In the code behind razor.cs file, IJSRunTime or others can be injected with the [Inject] attribute public partial class BillingDashboard ...
Read more >The 10 Most Common JavaScript Issues Developers Face
If you need help figuring out why your JavaScript isn't working, consult this list of the 10 most common JavaScript issues from a...
Read more >SpiderMonkey Internals
Design walk-through. At heart, SpiderMonkey is a fast interpreter that runs an untyped bytecode and operates on values of type JS::Value —type-tagged values ......
Read more >V8 JavaScript Engine - RSSing.com
Once the function becomes hot, this information is passed to V8's compiler, TurboFan, which generates optimized machine code. When the profiling ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@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 )
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 (https://github.com/dotnet/MobileBlazorBindings/issues/416)
maybe there’s some environment difference, though, and it’ll work for you?? I’ve posted it here: https://github.com/BenMakesGames/MBBPrintBug