Hmmm, we are having trouble recreating this bug on our end but I'm creating a ticket and will sort this out ASAP.
