I just deployed a change that should fix this. Try clearing your cache and refreshing the page. Sorry!