A script on this page is causing your browser to run slowly

[JoseSanchez]

Hi all

I adapted this script to my applciation and when it loads the Standard Style Internet Explorer shows the following error message:

"A script on this page is causing your browser to run slowly ...."

[ATTACH=CONFIG]20656[/ATTACH]


http://gmaps-utility-gis.googlecode.com/svn-history/r354/trunk/agsjs/examples/toc.html

[JeffJacobson]

Hi all

I adapted this script to my applciation and when it loads the Standard Style Internet Explorer shows the following error message:

"A script on this page is causing your browser to run slowly ...."

[ATTACH=CONFIG]20656[/ATTACH]


http://gmaps-utility-gis.googlecode.com/svn-history/r354/trunk/agsjs/examples/toc.html

IE does not run JavaScript as fast as other browsers such as Chrome and Firefox.  This is especially true of the IE version older than version 9.

Which version of IE are you using?

[Jean-PaulZagarola]

IE does not run JavaScript as fast as other browsers such as Chrome and Firefox.  This is especially true of the IE version older than version 9.

I also noticed this issue when running IE to load our Map ap. If you tell it to continue running the script the same error message pops up if you tell it to stop running the script you loose the functionality of the map. I tested this on an older computer with an older version of IE but this apparently is also an issue with newer versions using a newer much faster computer. The purpose of our map is to distrubute water quality data to our community members on a monthly basis and the app can potentially be very useful to do that. We are a bit worried however that the ArcOnline Web app might not be accessible to those who don't have fast internet speeds, most updated browser, or most recent computer hardware.

Is there anything we can do to increase the upload speed of our Map ap? Do we need to remove data layers potentially to increase upload speed even if they are not active? Upon loading there are only 4 active layers, which doesn't seem like once, though we have several layers that can be activated.

http://bit.ly/WK8soE

Thanks,

[AdrianMarsden]

UP to recently all was fine in IE 8 for us, mainly because we use Google Chrome Frame to get IE to run everything in Chrome.  However we have a few PCs that don't have this installed.  For them, IE8 simply fails affter a few map operations.

It was fine until recently - anyone any hints on how to track down whatever it is I have added IE doesn't like?

Cheers
ACM

PS - I found what was killing IE 8/9 - I'd added a snapping layer that was our fine detailed basemaps.  When zoomed in to a level these switched on AND in an urban area, IE just couldn't cope with that amount of vector data getting sent locally (I guess)

I rural areas, without so many features it could cope.

[JianHuang]

Client side doesn't implement spatial index, so snapping manager has to scan all available geometries to find the proper point to snap to. For IE8, the javascript engine is quite slow compared to other browsers. When the number of features gets large, it will be an issue.

[JoseSanchez]

The solution: http://support.microsoft.com/kb/175500