Thank you for confirming this on your end, @timchen!
Indeed, this was fixed in 1.4:
Moving to Fixed Bugs.