IE8 web map application problem

[GabrielZawadzki]

A map of county outlines created in ArcGIS Explorer Online and published as a web mapping application works perfectly when viewed in Firefox, Safari, and IE9. When the web mapping application is viewed in IE8, however, it fails to load and gives the message:
"Stop Running This Script? A Script on this page is causing Internet Explorer to run slowly. If it continues to run, your computer might become unresponsive." When "no" is selected, IE becomes unresponsive and will pop up the same message after about a minute. The map may show up behind the message, but it is not functional, and the legend and description do not load at all.

Similar problems are encountered when sing IE8 to view the map in ArcGIS.com Web Viewer.

The web mapping application can be viewed at: 
http://apps.arcgis.com/hosted/TwoPane/chrome/index.html?appid=d7f6321c201b474d96a2b5b228642a9c&webma...

Does anyone have some idea what the underlying problem might be? much larger map layers available in arcgis.com display perfectly as a web map application in IE8. Could this be a data pre-processing issue? The shapefile was simplified when it was uploaded.

Regards.

[MikeMinami]

Shapefiles, CSVs and GPX files added to the map are all drawn by the browser. You are running into limitations of the IE browser's ability to draw features. IE 7 and 8 are not able to handle the number of features in this map. The only solution is to generalize the data even more than ArcGIS Online can do. If you have ArcGIS Desktop, you can generalize your data more so that it can be viewed. Another solution is to host the data on ArcGIS Server.

Thanks,

Mike

[GabrielZawadzki]

Thank you for that clarification.

Unfortunately ArcGIS desktop and ArcGIS Server are not options. I'll try to generalize the shapefile in MapWindow GIS, uDig, OpenJUMP, or Quantum GIS. Is there a method (other than the web map application failing in IE8) to tell if the number of features is too large?

Regards.

[MikeMinami]

No, there isn't really a way. The polygons have too many vertices is the problem...

Mike

[mr_ProgMan]

Hello, everyone!

I have same problem in IE 8 (Stop running this script? ...) when the following code is running:

 
function setinfoWindow(objects){
    var ft = [];
    for (var cyc = 0; cyc < objects.length; cyc++){
        var feature = objects[cyc].feature;        
        var hidden = "<a onclick = 'showDetails("+cyc+")'> �?од�?обно ... </a>";
        var template = new esri.InfoTemplate(null, '${'+objects[cyc].displayFieldName+'}'+hidden);
        feature.setInfoTemplate(template);
        ft.push(feature);
    }
    alert(ft.length); // THIS WILL DISPLAY 5. not too much to display running timeout
    
    
    map.infoWindow.show(mousePoint);
    map.infoWindow.setFeatures(ft);     // HERE IS A PROBLEM
}

identified objects are polygons with 5 fields.
is there any solution for IE8 to work without "Stop running this script? ..." message?
any other normal browsers have no problems.

Thanks for any help.

[kylevalkenburg1]

I am seeing a similar problem in a js web application that, again, works fine in Chrome, Safari, and Firefox.  Any version of IE wants to quit running a script that loads up a      state polygon layer's info window (pop-up). I know that this is an IE issue.  The states layers is coming from an ArcGIS service.  Creating a new more "generalized" service is probably out of the question for tight now.  Is there a way to modify the application code to not request the geometry of the feature before it loads the info window?!?!?!


Thanks
KV

[NiketPhuria]

Hello All,

Regarding the issue that you are facing. Please refer to the following link: http://help.arcgis.com/en/arcgisonline/help/index.html#//010q00000007000000 and navigate to map Section to the following question: "I am having issues working with web maps in Internet Explorer 7 and 8.
The answer is "For the best performance viewing and creating web maps, it is recommended that you use Mozilla Firefox, Google Chrome, or Internet Explorer 9 or higher. Internet Explorer 7 and 8 are supported but have performance limitations when working with web maps. For example, you cannot drag and drop files onto the map, fewer features can be displayed, and you may lose your work if you leave the map viewer window without saving. If you need to use IE 7 or 8, installing Google Chrome Frame may improve your experience. The free Chrome plug-in allows your older browser to take advantage of newer web technologies in applications such as the map viewer."

I hope this will answer most of your queries. If there is any more question or queries; please feel free to ask me.

[MikeMinami]

@Kyle,

Here's some input from one of our developers on this...it may help.

I don't think there's a way to not request geometry, but I would ask him to confirm that maxAllowableOffset is being set and specified when his service is queried to ensure that a generalized geometry is being returned. He might need to upgrade the version of the API his template is using if he downloaded it months ago.

He can check that maxOffset is being sent by looking at the request in chrome dev tools, see attached screen shot.

Thanks,

Mike

[kylevalkenburg1]

@Kyle,

Here's some input from one of our developers on this...it may help.



Thanks,

Mike

My developer has checked out your suggestion and also pulled in the newest API.  NOW, in IE8 the application can't even load without throwing script errors.  Of course, the application runs beautifully in Chrome.

Before he sent me a new application, I tested some simplified services that I created and I had simplified my state layers down to 5 miles, and still not all of them were working (script error on identify).  I looked at the size of the requests, and the boundaries of the states are down to about 100-300KB (so eve my developer is convinced that the size is not the problem), and for some reason they all work fine, EXCEPT for FL and LA.  Extremely frustrated.

Thanks for the ideas though. 
KV

[kylevalkenburg1]

I finally got IE to work with the application.  There was no code fix here. I edited one of my simplified versions of the state data (5 miles) and I spent a morning projecting, editing, selecting and deleting features to eliminate a couple thousand unnecessary polygons (island/slivers).
 
IE8 must just really be bad at rendering.  Any other browser works fine, even with the original (huge) data.

KV