Hi, I am seeing double map click events when using Chrome. This also results in receiving a click event after panning the map. It appears the extraneous mouse event is being sent from _mouseClick -> _fire somewhere in the map source. The "correct" mouse event is being fired from _fireClickEvent -> _fire.
You can see the click after pan behavior with this sample:
I believe this issue is related to using it on a computer that also has a touchscreen. Using the touchscreen only (and not the mouse) does not produce this behavior.
