Now I remember; will it be possible that the previous behavior was
due to something in the last release of Three.js and now is fixed? If
the answer is no, then it will be worth reimplementing but also add it's
counter part after the scale takes place; this is, do the same in
resetCamera().