IE problem : to avoid teardown problems with IE, deactivate controls first

[cph]

If the controls of a map are not deactivated before layers are destroyed, then IE will report JS problems as the controls (Point, Drag) will not have a layer to destroy.

Patch attached.

[elemoine]

Could you provide a patch with the appropriate path - do svn diff at OpenLayers root dir.

Also, for your patch to have better chance to make it into trunk, provide tests. See  http://trac.openlayers.org/wiki/CreatingPatches.

You can mark the patch as review (Keywords) once it's ready for review.

[euzuro]

to me, this doesn't seem like the right approach to fix this problem. I don't think a control should have to be deactivate()d in order to be destroy()ed without causing errors.

This either means that we need to add a call to this.deactivate() in the generic control class's destroy() or else change the logic in the individual controls so as to avoid this error.

[crschmidt]

Having realized how old this ticket is, I think that this can likely be closed as invalid at this point. We did a fair amount of work on this in Feb/Mar at our code bunker, and I think we excised all the issues at that time. If that's not the case, then a simple example of a setup that continues to reproduce the error should be attached, and the ticket reopened.