This has been fixed. Thanks for reporting.