Thanks for the confirmation. I'll try and reproduce the issue on my end and hopefully release a fix in an upcoming build.
