Yeah, that fixed it, but it definetely changed from 2.0.5 to 2.1.0. I reproduced it by going back a version and testing it.