No worries, we actually recognize that bug and are currently working to fix it. Thanks for letting us know!