I've ran into that bug too, reloading the page seems to fix it. Did that happen in the web version?
Yes, web.
