Issues with Chrome?
Has anyone run into problems displaying an html5 viewer (1.3.1) in Chrome? When I have a fairly large Chrome window open, sometimes the banner and layer tree get blanked out. Also, cached basemap layers don't display.
I'm wondering if it's got to do with resolution/image size limits. But it works fine in IE10 and Firefox.
Thanks
Chris
-
Hi Chris. How large are we talking, pixel-wise?
When this happens, you can press F12 to view Chrome's developer console. Under the actual "Console" tab, you may be able to see some sort of error or warning that may or may not be helpful.
- Jason
0 -
No luck with Fiddler - no errors are reported. It happens at variable browser screen widths - depending what layers are displayed. I'm displaying all the layers as PNG32, and some of them get quite big (~150k). I wonder if it's possible there's is a limit in Chrome to the size of the images that the viewer mashes together to render the final map???
0 -
Do you happen to have a public viewer that I could look at? I'd love to poke at this using Chrome's developer tools.
0 -
I have also noticed this problem. resizing the viewer window bring back the layer list and/or the toolbar, but then for some reason they will drop out again sometime later. It appears as if the Layers are still there as randomly clicking in the white spaces will toggle layer visbility. My screens are 24in monitors with 1920x1200 resolution.
/customer/servlet/servlet.FileDownload?file=00P6000000elu41EAA
i tried looking at the Chrome's developer console (F12), but don;t understand what much of it means.
thanks
Ben
0 -
I just ran into this, randomly, on a customer's 1.2.1 viewer using Chrome 32. I'm on a 1920x1080 resolution. Unfortunately this appears to be a rendering issue in Chrome. Like Ben points out, all of the elements are still there and remain interactive, they just happen to be whited out. We'll poke around and see if we can find anything on our side causing this issue.
0 -
I have found a solution : http://forums.arcgis.com/threads/101168-Google-Chrome-Screen-blanking-issue
this.app.map.fadeOnZoom = false;
this.app.map.force3DTransforms = false;
this.app.map.navigationMode = "classic";0 -
We are experiencing this issue with some sites more than others - which really seems strange. I think this is really more of a Chrome issue than a Geocortex viewer issue but I really need a resolution.
I have looked at Vincent's posting and understand what he is talking about. However, I can't figure out where you change those values in the HTML 5 viewer since the map creation is handled by the framework.
Any suggestions?
Bryan
0 -
Hello! I also think it's a Chrome issue. To fix the problem, I had to create a custom module. In it, you have to set the map properties right after it's loaded.
initialize: function (config)
{
this.inherited(arguments);
this.app.eventRegistry.event("MapLoadedEvent").subscribe(this, function (eventArg)
{
//
// Fix the blank spaces glitch
this.app.map.fadeOnZoom = false;
this.app.map.force3DTransforms = false;
this.app.map.navigationMode = "classic";
});
}0 -
Thanks for the help Jason and Vincent - I think we have it fixed.
I did make a small code change on Jason's example. The "this.app.map.xxxx" properties weren't available so the code didn't work. The MapLoadEvent returns the map object in the eventArg so I changed the code as follows:
viewer.eventRegistry.event("MapLoadedEvent").subscribe(this, function (eventArg) {
eventArg.fadeOnZoom = false;
eventArg.force3DTransforms = false;
eventArg.navigationMode = "classic";
});After that all is well.
0
Please sign in to leave a comment.
Comments
9 comments