Thank you for pointing this out, @StrangeTech!
Indeed, this should now be fixed with 1.4.0.3.
Moving to Fixed Bugs.