I am having the exact same issue as of today and after inspecting their Javascript code it turns out there is a typo that breaks the page's behavior. I just reported a bug using Feedback Assistant, but I'm surprised no one had answered this earlier.