I created a bug (sorry I should have created a forum post first) that pointed out how double clicking a point from a KML entered tracking mode.
https://github.com/AnalyticalGraphicsInc/cesium/issues/2649
Two questions:
Why is zooming to the object and entering tracking mode the default double-click behavior?
Why is the solution to avoiding this is to override double click behavior as seen from the response in the link above?
KML can include all kinds of data, including data that it doesn't necessarily make sense to "track".
I'm sure I'm about to be informed of the reason behind this but my assumption is that if I load a KML it is up to the developer to decide what double clicking an object does. Given that it defaults to tracking mode I would have also assumed there would be an optional way to disable tracking instead of writing this code to disable it:
viewer.screenSpaceEventHandler.setInputAction(function(e) {
var picked = viewer.scene.pick(e.position);
if (Cesium.defined(picked)) {
var id = Cesium.defaultValue(picked.id, picked.primitive.id);
if (id instanceof Cesium.Entity) {
var entity = id;
if (Cesium.defined(entity)) {
viewer.zoomTo(entity);
}
}
}
}, Cesium.ScreenSpaceEventType.LEFT_DOUBLE_CLICK);