Thanks for letting us know. We've fixed that bug now.