It worked fine after I closed the page and entered again, but I thought I would report it anyways since it seemed super funky.

Hm, yea. Seems like some sort of browser malfunction. Looks like the script got all confused upon initial load or something.

If something like that happens again, I'd suggest just performing a hard refresh on the page and I would imagine it'd resolve most issues like this.