ASPxDocumentViewer - Print Report button does not work after Google Chrome Update 76.0.3809.132

Hi,

Missclicked the hotfix, we already tried Yaroslav’s solution and it worked. I do not need the hotfix.

Thank you.

Hello Alexandre,

Thank you for your clarification. I believe that the hotfix for this issue will be useful to other customer.

Thanks,
Elliot

Hello, I have the same error described in ticket, but with the v16.2.4 and Chrome Update 77.0.3865.75
What solutions do we have for this version?

Hello,

If updating the ASPxDocumentViewer control is not an option for you, please consider the workaround provided by Yaroslav in this ticket.

Thanks,
Elliot

Hi,
We installed the hotfix 18.2.11 but when we click the printbutton, it throws an Error in Chrome: Cannot read property 'contentType' of null
The error occurs on: if(f.contentDocument.contentType !== "text/html")
We use the DocumentViewer Extension

Screenshot is attached
is there any solution?

I've tried,  successful,

Thank you…

Hi,

We are using version 14.1.6.0 and due to some reason we can't update the version. I tried the workaround but failed.

My .aspx:
<dxxr:ReportViewer ID="ReportViewer1" runat="server" CssFilePath="~/App_Themes/RedWine/{0}/styles.css"
                                CssPostfix="RedWine" SpriteCssFilePath="~/App_Themes/RedWine/{0}/sprite.css"
                                LoadingPanelText="">
                               <ClientSideEvents PageLoad="init" />

<LoadingPanelImage Url="~/App_Themes/RedWine/Web/Loading.gif">
                                </LoadingPanelImage>
                                <LoadingPanelStyle ForeColor="#303030">
                                </LoadingPanelStyle>
                            </dxxr:ReportViewer>

Javascript Error:

Uncaught TypeError: Cannot read property 'printHelper' of undefined

Please help!

I think i have fixed it by making some changes to the init function:

function init(s) {
            var isChrome = /Chrome/.test(navigator.userAgent) && /Google Inc/.test(navigator.vendor);
            var createFrameElement = s.printHelper.createFrameElement;

s.printHelper.createFrameElement = function (name) {
                var frameElement = createFrameElement.call(this, name);
                if(isChrome) {
                    frameElement.addEventListener("load", function (e) {
                        if (frameElement.contentDocument.contentType !== "text/html")
                            frameElement.contentWindow.print();
                    });
                }
                return frameElement;
            }
        }

thks anyway.

Hello Yong,
 
Thank you providing a workaround for the 14.1 version. I believe it can be useful for other customers.
 
Thanks,
Elliot

Hello,

I am using DevExpress Version 17.1.6.0. Currently, the ASPxDocumentViewer print feature does not work with the Firefox 69.0 update. Could you help?

Hello,

I've created a separate ticket on your behalf (T815156: The ASPxDocumentViewer print feature does not work with the Firefox 69.0). It has been placed in our processing queue and will be answered shortly.

Hi,
We use dx:ReportViewer and dx:ReportToolbar.
Our devexpress version is 16.1.5
Unable to change to AspxDocumentViewer.
How can activate the print button.
Thanks a lot

Hello Selim,

Please consider the workaround provided by Yong Xiang Tay in this ticket to avoid this issue.

Thanks,
Elliot

As stated on the blog post in regards to this issue, this also appears to affect ASPxWebDocumentViewer. Attempting to print from the preview screen of the ASPxWebDocumentViewer, results in no print job being generated, or it being rejected.

I've been testing this on 18.2.9.

Thank you for mentioning this issue in this thread, Mark.

We'll research it in the context of the Web Document Viewer - Print Report button does not work after Google Chrome Update 76.0.3809.132 thread.

Do you know when the hot fix will be ready?

Hello,

We have already published the hotfixes for this issue so that you can install the required hotfix and check whether the issue is solved.

Thanks,
Elliot

Would there be a hotfix for 17.2 or 17.1?

Hello Rudolf,

17.1 and 17.2 are outdated builds, so we do not provide hotfixes for them. If the upgrade of your application to a new version of our controls is not an option for you, use the workaround provided by Yaroslav to avoid this issue.

Thanks,
Elliot

I have the same problem in version 19.1.6 and it seems that above links to 19.1.7 are broken, where can I find it?

Please ignore my previous comment-question, after refreshing the page I managed to download the patch of 19.1.6 that solved the problem, however  warning message "Resource interpreted as Document but transferred with MIME type application/pdf" still shows.

Hello Nikos,

Would you please prepare a screencast that illustrates how to replicate this issue? For example, use the Jing or ShareX tools for this purpose.

Thanks,
Elliot

Maybe better version with check for null

JavaScript
function init(s) {  
    var createFrameElement = s.viewer.printHelper.createFrameElement;  
    s.viewer.printHelper.createFrameElement = function (name) {  
        var frameElement = createFrameElement.call(this, name);  
        if(ASPx.Browser.Chrome) {  
            frameElement.addEventListener("load", function (e) {  
                if (frameElement.contentDocument && frameElement.contentDocument.contentType !== "text/html")  
                    frameElement.contentWindow.print();  
            });  
        }  
        return frameElement;  
    }  
}  

There is an error in console that frameElement.contentDocument is null

Hello Jan,

Thank you for your clarification. I have corrected Yaroslav's answer in this ticket.

Thanks,
Elliot

Maybe important is also include this fix also to hotfix release.

Hi all

error in console that "Uncaught TypeError: Cannot read property 'printHelper' of undefined" please refer the attachement

I am using 14.2.4 version and can not be upgrade

Hello Chandana,

I've created a separate ticket on your behalf (T818267: Print Report button does not work after Google Chrome Update). It has been placed in our processing queue and will be answered shortly.

Hello Jan,

Note that we do not provide hotfixes for outdated (old) builds. If the upgrade of your application to a new version of our controls is not an option for you, consider using the workaround provided in this ticket.

Thanks,
Elliot

I am having the same issue with DevExpress 13.1.14

Hi Duc,
Did you have a chance to try the above workaround? Does it work for you?

HI

I did try it and it takes a while before the Print Dialog Screen appears – as if you selected CTRL – P in chrome.
So the workaround works – now I have to add this to about 20+ forms for each Report View control…

Kind regards

Stuart Lowe

Is it possible to have a hotfix for this available for DevExpress 18.1.3?

Using the 18.1.13 hotfix would require us to upgrade our version of DevExpress that we use, which we are not prepared to do at this time.

Is it possible to get a hotfix for this issue on DevExpress 17.2.4?

Hi,
As you probably know, here at DevExpress, we follow the continuous integration model. The version you mentioned (v17.2.4) is very old and its life cycle has already ended. Unfortunately, we won't be able to prepare a hotfix for this version.
If you're unable to update, consider using the workaround I provided above.

Regards,
Yaroslav

Thank you Yaroslav,
I am now updating the project from 17.2.4 to 19.1.6. (i could not find 19.1.7)
Does the hotfix work on 19.1.6 as well as 19.1.7?
Ron

When the ticket's status is "Fixed", this means that the corresponding issue has been fixed, and the fix will be included in the next public release. Version 19.1.7 is not yet here. At the same time, version 19.1.6 was released prior to this inquiry report and therefore it does not contain the required code changes. If you do not want to wait for the next build release (v19.1.7), you are welcome to try a hotfix (an intermediate build) immediately. The current hotfix version is 19.1.6.19269.

Regards,
Yaroslav

Hi Yaroslav,

This solution I applied to  Version  14.2, but it did not work.Please let me how I solve this on version 14.2.

You provided Javascript above for the old ReportViewer control:

"If you're using the old ReportViewer (with our without ReportToolbar), change the handler as follows:"

However, I couldn't find a ClientSide Init event for this control, or for the toolbar. Is there a way to handle this issue for the ReportViewer control?

Thanks!

@Janaka,
I see you've already created a separate ticket regarding this matter: Web report toolbar print buttons do not work in Google Chrome.
Let's continue our discussion there.

@Julie,
Use the client-side "PageLoad" event instead. I've updated my answer to avoid any ambiguity.

I had the same problem this week, thanks to all this comments i have solved, applying the Yaroslav's suggestion https://docs.devexpress.com/eXpressAppFramework/113612/task-based-help/reporting/how-to-access-the-document-viewer-and-web-document-viewer-controls, I used the HTML5 at ReportsAspNetModuleV2.ReportViewerType property, The same problem occurs if i ran the application in Microsoft Edge and FireFox, all of them where solved. I still using 16.2.6 version.

Thanks

Regards.

You're very welcome, Pedro! I'm happy to hear that my solution worked out for you.
Should there be further questions, feel free to contact us at any time.

Regards,
Yaroslav

Hi Yaroslav.

I realize today that i have a couple of apps which continue using the old report module (No, the ReportModuleV2), so, is there any solution for it?.

Any suggestion?

Regards.

Pedro,
If you have to stick with the old ReportViewer / DocumentViewer component, use the code approach I provided above. It can be implemented both in a regular ASP.NET application or in a XAF application. The only difference here is that in XAF the viewer is created for you, so you have to use a XAF-specific API to register your custom client-side event hander, exactly as my colleague explained in the ASPxDocumentViewer ver. 16.2.4 - Print Report button not working after Google Chrome Update 77.0.3865.75 thread. If there are any issues with this approach, please post a reply in that thread and elaborate on what you've tried and what issue you encountered (whether it's a compilation error, a runtime error, etc).

Regards,
Yaroslav

Hello I've update my devexpress components to the 18.2.11 version that apparently solves the print problem for Google Chrome browser but when I've tried to use the reporter it throws me an error Cannot read property 'contentType' of null can anyone help me solve this problem?

Hi,
The same runtime error has been already reported here: A java script error when printing a report from the ASPxDocumentViewer control in Chrome v77. Unfortunately, our attempts to reproduce the same issue using v18.1.11 were unsuccessful. If you have a demo project that we can test on our side, or if you aware of any steps that one should follow to reproduce the issue, please let us know in the comments section of the A java script error when printing a report from the ASPxDocumentViewer control in Chrome v77 thread.

Regards,
Yaroslav

Hi,
I am using 14.2.6.
The workaround is not working for me. I had ASPxDateEdit component on the report aspx to allow user to define the period. The calendar will not appear when I click on ASPxDateEdit after Iadded the javascript.
Pls take note that I have the  ASPxDocumentViewer  in  a UserControl file (.ascx)
Please advice.
Thank you.

Hi Liow,
It's highly unlikely that the issue your face has anything do with ASPxDateEdit. Rather, it's a script error that prevents the editor's correct execution. You should be able to see this error while running your project and opening the developer tools of your browser, the "Console" tab (F12).
There are two major reasons why the code you have put into your UserControl does not work:

1. The "Init" handler must be defined before the viewer and not after.
2. There is no "ASPx.Browser.Chrome" constant in the version you're using: you have to use a regular expression instead (see the alternative solution posted above).

For your reference, I've attached the sample project that target v14.2. Please check it and confirm that it works for you.

Regards,
Yaroslav

I need a fix for DevExpress 14.2

We use ViewControllers.

Hi Alexa,
I see that you already created a separate ticket regarding this matter: Printing not working, [could be] after Chrome update. We'll reply to you there as soon as possible.

Regards,
Yaroslav

This support article was very helpful. I also wanted to point out that this also fixes the same bug when trying to print a WebChartControl in Chrome.

Inline Code
<dx:WebChartControl ID="xChart" ClientInstanceName="xChart" Width="982" Height="640" runat="server">
<ClientSideEvents Init="init" />
</dx:WebChartControl>

Hello Todd,

Thank you for sharing your source code. I believe that it will be useful to other users who try to accomplish a similar task.

Thanks,
Elliot

I am using the AspxDocumentviewer in Asp.net web form with devexpress version 19.1.6. After chrome update the AspxDocumentViewer print button is not working. I have tried to fix the issue by adding the script below. But still it is not working. Do I have to install the latest version of devexpress to fix the issue?

JavaScript
<script type\="text/javascript"\> function init(s) { var createFrameElement = s.viewer.printHelper.createFrameElement; s.viewer.printHelper.createFrameElement = function (name) { var frameElement = createFrameElement.call(this, name); if(ASPx.Browser.Chrome) { frameElement.addEventListener("load", function (e) { if (frameElement.contentDocument && frameElement.contentDocument.contentType !== "text/html") frameElement.contentWindow.print(); }); } return frameElement; } } </script\>