This fix is from 1.5.2.0 release notes:
So perhaps it’s either an intentional change or a bug introduced by this fix.