Ironically, the page is ridiculously bugged on a current browser - Chrome 1.0.154.65.