By reading through some of Telerik's responses, it seems like this PDF is embedded with a command to cause the print, but that's the problem that Chrome has patched out. If you look at the javascript that is being used by the ReportViewer object, you can see that we the ReportViewer is rendering the report to PDF in an iframe. What this does is overrides it with a nearly identical version of the PrintReport function, with one major difference. Any browser without a PDF plugin will just ask to save the document first, there's no way around that of course. print() on the opened iframe window which will work in any browser as long as it has a PDF plugin installed. The issue in Chrome is that the iframe itself can't have JS to tell itself to print but the calling window opening the iframe still can still issue a print command.Īs per my last comment, when using the HTML5 report viewer you can either modify the JS source to add the 2 lines in (which was previously suggested by Nasko) or add the following JS in to modify the print function to call. I don't think you specifically need to use PrintJS to print the report as that will just internally be calling window.print() anyway, all you need is to tell the iframe window to print.
0 kommentar(er)
