Thanks for bringing this to our attention! Our QA team was able to reproduce the bug and is investigating the issue.