Completed
Last Updated: 18 Sep 2019 16:03 by Naumand
Luca Galbiati
Created on: 12 Sep 2019 10:51
Type: Bug Report
48
Print Dialog doesn't appear in Google Chrome 77.0.3865.75

The print functionality cannot be used in Google Chrome 77.0.3865.75 (lastest update).  The following error is displayed in the console of the browser: Resource interpreted as Document but transferred with MIME type application/pdf.

As an alternative, you can use other web browsers for printing. 

15 comments
Naumand
Posted on: 18 Sep 2019 16:03

This one is not an accepted solution for thousand of end users and hundred of companies that are waiting for your release. Opening the report may be an accepted solution if you are in report viewer and click on print icon, but not when we  want to use direct print ( .PrintMode(PrintMode.ForcePDFPlugin)) for specific reports.

  1. The browser will first block this new window from opening automatically like the image below

 

   2. And  most important the user will have to still click CTRL + P  (after allowing the browser to open this kind of links)

 

Will this be you final resolution for this issue ? Opening the rendered PDF in a new tab ?


 

 

Licencias
Posted on: 18 Sep 2019 16:01
and those of us who have version 12.2.18.1129 and cannot update to the new version, how can we fix the problem?
ADMIN
Nasko
Posted on: 18 Sep 2019 15:42
Hi,

You can download the new R3 2019 release where the print button of the HTML5 Report Viewer now renders the report for print purposes and opens it in a new browser tab. The auto-print script is still embedded in the document, but Google Chrome will wait for user interaction in order to show its print dialog.

We are now testing more rigorously against the beta/canary build of Google Chrome so we are positive that such issues will be avoided in the future.


Dealing with this Google Chrome restriction in the obsolete ASP.NET WebForms report viewer would require to either upgrade to the HTML5 Report Viewer or to perform other actions on click of the print button by overriding the print function like so:
<script type="text/javascript">
    ReportViewer.prototype.PrintReport = function()
    {
      //do stuff
      this.PrintAs("Default");
    }
</script>


Regards,
Nasko
Progress Telerik
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Lisa
Posted on: 18 Sep 2019 15:33
Was this fixed in today's release?
Jennifer
Posted on: 18 Sep 2019 14:57
Do you know when this will be fixed? 
Developer
Posted on: 18 Sep 2019 07:15

What is the equivalent workaround (by using printMode) for the old Telerik web form report viewer (Telerik.ReportViewer.WebForms.ReportViewer) ? We are using it and hundred of customers are struggling with the print issue. 

We need at least a workaround ASAP.

Pete
Posted on: 17 Sep 2019 18:43

This really worries me. I am losing confidence in the testing that is being done on these releases. We had to back out the last release because of an issue with defaulting data on grids. Now it appears they are not properly testing new versions of browsers. Like Concept said below, we also love the controls, but they cannot slip on quality. We have hundreds of users using the system, something like this is crippling to us. Telling them to use a different browser (away from their standard) is a low quality answer.

Mike
Posted on: 16 Sep 2019 15:50
Note line numbers and variable names may be different for you.  So just look for case sensitive "IFRAME".  The code will be soon after that.
Mike
Posted on: 16 Sep 2019 15:21

I would not recommend this moving forward but if you need a fix/workaround now. Here is what I did.  I deminified the file telerikReportViewer-##.#.#.###.min.js. Around line 580 you will see the code in the function called "e"

o.body.appendChild(t);

That is the code where the warning/error is thrown. Just after that line add the following code.  This will force the print.

t.contentWindow.focus();
t.contentWindow.print();
ADMIN
Neli
Posted on: 16 Sep 2019 14:39

Hello,

 

I would like to thank you for the kind words and the feedback which I forwarded. We have already taken action against such issues in the future. Hopefully, this problem will not be replicated anymore.

 

Regards,
Neli
Progress Telerik

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Concept
Posted on: 13 Sep 2019 19:52

Thank you for working on it. We are eagerly waiting for the fix. Our customers are printing several reports each day and this problem really affects them.

I also have a feedback and I will appreciate if you can share it with your managers. Progress / Telerik is a big company and we expect you to test each version of Chrome vigorously when it is still in beta. 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.

After every new release of Chrome, we feel very anxious that something in your controls will break with the new version. It happened a couple of times so far, and this really bothers us. I think it also hurts your credibility and our trust on you. You should invest more on testing each new browser version when they are still in beta. You should also test your new versions better. We also had problems with some bugs in your new versions. 

We love Telerik controls and we believe you can take care of this. 

ADMIN
Neli
Posted on: 13 Sep 2019 12:42

Hello,

We are sorry for the inconvenience this causes. We are doing our best to include the fix for the issue in our new release on Wednesday (18th of September). Once it works, we will post an update in the post and you will receive an email notification for that.

In general, the printing functionality is based on rendering the report in PDF format with special settings so when the PDF file opens in a browser, the PDF plug-in's Print dialog is directly invoked. By default, the viewer widget tries to use the PDF plug-in of the browser for printing. You can manually control the printing behavior through the printMode option when creating the report viewer widget.

This is the possible workaround at the moment.  By setting FORCE_PDF_FILE printMode option, the widget will always export the report document to a PDF file with the special print script. For more information, check Printing Reports article. For example in the HTML5 Report viewer, you need to add the following line in the initialization of the viewer:

printMode: telerikReportViewer.PrintModes.FORCE_PDF_FILE

 

Regards,
Neli
Progress Telerik

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Đình
Posted on: 13 Sep 2019 08:18
Give me the solution to fix it as quickly as possible, thousands of customers are waiting.
Adam
Posted on: 12 Sep 2019 22:27

I have been seeing this exact situation with our reports; it appears that it was an intentional functionality change from Google:
https://pdfium.googlesource.com/pdfium.git/+/2021804f1b414c97667c03d7ab19daf66f6a19ef


It indicates that a mouse gesture/event may be required in order to allow the print.  Going to experiment, but that may be of use to some.

ADMIN
Neli
Posted on: 12 Sep 2019 11:13
Hi,

We will let you know in this post if there is a workaround which will allow the usage of the print functionality in the lasted version of Google Chrome (77.0.3865.75).

Regards,
Neli
Progress Telerik
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items