Thank you for your information! This issue should have been fixed in the latest nightly builds, but we'll double check to make sure.
