That's a bug the site has with Firefox, which we haven't gotten around to fix yet. It does work properly in Chrome/Safari/IE, tho.