Hmmm. Sorry, Frank. It had a piece of JavaScript that wasn't playing nice with Firefox. Should be fine now though.