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