Once again, thank you for reporting this @lukelee!
This should now be fixed with 1.4 :
Kindly let me know if this is the case on your end. Thank you in advance.