It happened a couple of times so far, and this really bothers us. Chrome 77 beta version was available almost a month ago, so if you had tested it when it was beta, the fix was going to be ready before the final release.ДЄfter every new release of Chrome, we feel very anxious that something in your controls will break with the new version. Progress / Telerik is a big company and we expect you to test each version of Chrome vigorously when it is still in beta. I also have a feedback and I will appreciate if you can share it with your managers. Our customers are printing several reports each day and this problem really affects them. We just wanted to give this back to the community since, for many of us, the solution of 'download the new version and migrate to HTML5 ReportViewer' is simply unacceptable.

All testing has indicated that this workaround behaves as expected. We decided to do this because we were also having a problems with the webform workaround adding and moving things in our report. What we're doing with this solution is waiting for the iframe to load, and then sending that inner document to print using a browser supported method: execCommand('print', true, null) 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.

Chrome pdf viewer not working 2019