ASP.NET Core 6 MVC : return after window.print() not going through controller

Question

I have a gallery of images on a webpage and a "Print" button which then calls the browser print using window.print().

<button class="button current" id="printButton" onClick="window.print()">
Print
</button>

I have also used some CSS using @@media print to specify the page size.

This works very nicely and I have found no good reason to make this more complicated. However, when the user has completed or cancelled the print, it returns to the page and seems to refresh the page without triggering the controller. This loses various setting that have been sent to the page via the controller using ViewBag and TempData.

I don't really understand what is refreshing the page without a call being made to the controller, neither HttpGet nor HttpPost pick this up. Any suggestions?

Perhaps the issue you are facing may have to do with the respect in the way the browser is handling the print function window. When the print dialog is closed (either through printing or through cancellation), sometimes the browser may simply refresh page. — Esanju Babatunde
– Esanju Babatunde, Commented Aug 31, 2024 at 18:39
You can try other method to persist your data even if there is a refresh on the page. 1. Use Session instead of ViewBag/TempData 2. Store the data inside cookies and retrieve back when the page refresh 3. Create a separate action that returns a view designed for printing. I hope this can be of help — Esanju Babatunde
– Esanju Babatunde, Commented Aug 31, 2024 at 18:47
What you mean viewdata missed? I found the viewdata will not missed even you use the print method. — Brando Zhang
– Brando Zhang, Commented Sep 2, 2024 at 7:02

Fei Han · Accepted Answer · 2024-09-17 03:17:23Z

0

it returns to the page and seems to refresh the page without triggering the controller. This loses various setting that have been sent to the page via the controller using ViewBag and TempData.

Firstly, if the page is refreshed/reloaded, the request would be made from browser side and reach to web server and controller action, then generate view result and send response to browser.

For more information about ASP.NET Core MVC Request Life Cycle, you could check this doc: https://www.c-sharpcorner.com/article/asp-net-core-mvc-request-life-cycle/

Besides, if you'd like to prevent page from reloading/refreshing after you click print button to keep original inputs/contents, you can try to modify the code like below.

<button class="button current" id="printButton" onClick="window.print();return false;">
    Print
</button>

answered Sep 17, 2024 at 3:17

Fei Han

28k1 gold badge35 silver badges47 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

ASP.NET Core 6 MVC : return after window.print() not going through controller

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related