print widget not loading in Chrome

1417
3
08-18-2016 05:04 PM
SebastianRoberts
Occasional Contributor III

Hi, 

  I just noticed that our print widget has a timeout error when loading in Chrome (Version 52.0.2743.116 m).  I tested a few others and found similar errors. It even happened to me when trying out Robert's Calhoun County Viewer 3.1, so I know it isn't just another poor programming error on my part .    See screenshot below.  The network traffic doesn't show any errors.  It seems that the query to get print parameters from the service is returning a response. Anyone else having the same experience?

0 Kudos
3 Replies
RobertScheitlin__GISP
MVP Esteemed Contributor

Sebastian,

   if you would have gone to my 3.1.1 site you would not have seen the issue. Here is the thread where I provided the workaround and then esri came out with a patch:

https://community.esri.com/message/626951 

SebastianRoberts
Occasional Contributor III

Hi Robert,

  Thanks for your reply.  I updated the _getPrintTaskInfo function as you suggested in the post (and am using a proxy), but still get the same result.  The get request is using a proxy and returns the parameters, and I don't see any errors in the console, but the widget still doesn't finish loading.  If you are able, you could take a look my app at  https://gis.nevcounty.net/test/wab02/index.html

0 Kudos
RobertScheitlin__GISP
MVP Esteemed Contributor

Sebastian,

  Well I thought that it was issue with my change and WAB 1.3 so I added the code to my old 1.3 eSearch site that was not working in Chrome and it worked fine. So now I am trying to figure out what is different between our two site and the most obvious is the network protocol. You're using https and I am not, but that does not strike me as the issue. So I checked your code change to the Print.js and it look correct. then I found that you had already modified the Print.js for other stuff:

//Nevco Customization - added a function to process json before sending request
_modifyJson: function (args) {

So I have to wonder if any of that is affecting it. I would suggest you try a vanilla print widget with the proxy change an see if it works.

0 Kudos