Thank you for bringing this up to us. This is a bug our engineers are aware of and they are hoping to get this resolved by the end of March. I will keep this in tracking until then.
It looks like this bug was fixed, we're just a little late updating the status of this one. Thanks for the feedback!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.