ASPxDocumentViewer ver. 16.2.4 - Print Report button not working after Google Chrome Update 77.0.3865.75

Hello,

If updating the AXPxDocumentViewer control is not an option for you, please consider the workaround provided by Yaroslav in the ASPxDocumentViewer - Print Report button not working after Google Chrome Update 76.0.3809.132 ticket.

Thanks,
Elliot

Hello,

I have made the following proposed change in my Dafault.aspx file, but it still doesn't work. I have v16.2.4, what am I skipping?

Code:

ASPx
<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 && frameElement.contentWindow.print();  
                 });  
             }  
             return frameElement;  
         }  
     }  
 </script>  


 <dx:ASPxDocumentViewer ID="ASPxDocumentViewer1" runat="server" Height="763px" ToolbarMode="Ribbon" Width="100%" ReportTypeName="XtraReport1">  
     <ClientSideEvents Init="init" />  
 </dx:ASPxDocumentViewer>  

Hello,
I tried to reproduce the issue using the same code, but couldn't. I have attached a sample video to illustrate how everything works on my side. Would you please check out if any error occurs when you are printing a report in the Console tab of your browser's Developer tools and provide us with the screenshot off the tab if errors exist. It would be also great if you provide us with a runnable sample project where the issue occurs so we can research it on our side.

The thing is, that we have the problem using a xaf asp.net site.

attached is the result after appliying the solution proposed

Thanks!

Hello,

Please remove the following code from the Default.aspx page:

ASPx
<dx:ASPxDocumentViewer ID="ASPxDocumentViewer1" runat="server" Height="763px" ToolbarMode="Ribbon" Width="100%" ReportTypeName="XtraReport1">  
    <ClientSideEvents Init="init" />  
</dx:ASPxDocumentViewer>  

You do not need to add the ASPxDocumentViewer control, because XAF creates it for you. To access the ASPxDocumentViewer instance created by XAF and add the event handler to it, use the following solution: How to: Access the ASPxDocumentViewer and ASPxWebDocumentViewer Controls.

Note, XAF handles client-side events, too. If you add your client-side event handler, you can accidentally overwrite an XAF handler. To avoid this issue, use the ClientSideEventsHelper.AssignClientHandleSafe method to add a new event handler to a client-side event.

I had the same problem, thanks to this ticket i have solved with Yaroslav's suggestion (Using the HTML5 ReportViewerType). I just have a  doubt.

According with Uriah's last comment, there is no need to handle the client-side events, i mean, nothing to do at Default.aspx. I have tried both way , they works indistincly.

Regards.

Hello Pedro,

Our ASP.NET controls allow you to handle client-side events in code. This approach is useful in XAF applications, which create ASP.NET controls dynamically. Refer to the following ticket for the additional information: Handle Client-Side Events of DevExpress ASP.NET controls in XAF.