Hi @quantumodo,
Thank you for bringing this issue to our attention. We have successfully reproduced the problem you described. As @DevoDog mentioned, refreshing your browser can serve as a temporary fix.
We will work on addressing this issue in the next version.
Thanks for your understanding!