Pan mode lockup with Feature Layer in IE8

Question

Original User: vpatel

It seems that in IE8 when using Feature layers  the map has a tendency to lock up in pan mode when a lot of panning is done on the map. During the lockup just moving the mouse (without holding down the left mouse button) will pan the map.  This behavior only seems to occurs in IE8 . Firefox, Safari and Chrome don't have this issue with lot of panning.

The issue can be replicated using the example and panning around a lot :
http://help.arcgis.com/en/webapi/javascript/arcgis/demos/fl/fl_hover.html

Anyone - have any suggestions or workarounds (besides not using feature layer).

Thanks in Advance

PrintOutput.JPG

MapPrinterandDialog.zip

m.png

Request Rate Dataview expression.png

EdSaunders · Answer

Just wanted to say thanks for this solution, fixed it for me as well. Cheers.

Anonymous User · Answer

Original User: vpatel

Hi Derek - appreciate you looking into this, I will get back with you after running some tests.

Agree - I would prefer Steve's solution too , but since this is a public application no way to control end users choice of browser 🙂

Thanks again for your help.
 Hey Vijay,

Just sent you an email on this but I think the solution to the particular problem you're having is to set displayOnPan to false for feature layer. To target only IE, something like this does the trick:  
featureLayer = new esri.layers.FeatureLayer(url, {
  mode: esri.layers.FeatureLayer.MODE_SNAPSHOT,
  maxAllowableOffset: calcMaxOffset(),
  outFields: ["'*"],
  visible: false, 
  displayOnPan: (!dojo.isIE)
});

If it were up to me, I would prefer Steve's solution of not using IE ;) .

Anonymous User · Answer

Original User: vpatel

Thanks - I like your suggestion to not use IE , but we are stuck with the requirement to make it work in IE 😞

Yeah - don't use IE.

Just kidding - I've seen this before, too. I'm not an expert on this, but I think it's due to the way that IE renders features (it uses VML since SVG is not supported).

Ensure that you're serving the smallest possible features by using the maxAllowableOffset parameter - see the excellent blog post here regarding this.

Good luck,
Steve