Great, we'll look forward to reproducing and destroying this bug. Of course the best thing for us to do will be to do a comprehensive QA pass through Safari and FF rather than doing a "oh my god, the launch is tomorrow" runthrough. :)