Yeah, I was surprised by that too. And the commit message for that revision has nothing to do with that change. But, we actually call <code>computeBoundingBox</code> on the mesh every time we get the property, because the object might have moved since the last time the bounding box was calculated. I also did a quick sanity check on a couple of apps to make sure it still works, and everything looked fine.