I'm at least as happy as you guys are ;) For future reference what was happening was that I had a non-existent css file referenced in the pages. Every other browser ignored that and went on. Safari looked for the non-existent css file and somehow processed the 404 page as css resulting in the oddness you saw.