Yeah, I noticed that myself, but I kind of hoped it was a machine-specific problem and not a general problem with Safari.
