We've fixed this. Thanks for the bug report!