That’s a known bug which I didn’t have time to investigate/fix just yet.
Reloading the page fixes it usually.
