Thanks very much for reporting this! It’s now fixed.