I've reproduced the issue, and we're looking into a fix now.