I believe this issue was also resolved with the fix we put into place earlier today. Can you refresh the page and try again and let us know if you're still seeing the issue?
It is now working fine. Interesting, in that this appeared to be broken even when the other bug had been fixed, but regardless, all is good now.
Thank you Matt.