Oh no! Sorry to hear that. I have come across that bug before but I have not been able to replicate it since, I *think* doing a browser reload should get it back to working order. I'll have to look into what might be causing that bug.
