Looks like the page was cached in a bad state, we have flushed the page cache and this should now be fixed. Can you please confirm if you still see this issue?
Edit: it seems to still exists on the published page but not in the backend, there seems to still be some issues, we will review this ASAP.
Edit2: I think it is now fixed, can you please let us know if not?
