After testing myself with the latest release (1.66) I can confirm this has been fixed