Once again, thank you for bringing this up @T-low!
With 1.3, this should now be fixed. Please let us know if this is the case on your end.
Thank you.