Safari 5.1 and 5.0.6
New from Apple is Safari 5.1 for Mac OS X 10.6 Snow Leopard, which brings the company’s Web browser on par with the version installed on 10.7 Lion. Safari 5.1 includes several new features, including Reading List, which enables users to create a list of Web pages they can then examine at a later date; Resume, which automatically restores all open windows and tabs when you relaunch Safari; and a Privacy pane that makes it easier to remove browsing data from your system. In addition, Safari 5.1 supports a new process architecture that separates the user interface from rendering operations, providing better performance and more stability, particularly when using third-party plug-ins. Other
improvements highlighted by Apple include private auto-fill, better search functionality, drag-and-drop for moving files from the Downloads window, improved support for modern Web technologies like HTML5 and CSS3, and new APIs for extension developers.
Separately, the company has also released Safari 5.0.6 for Mac OS X 10.5 Leopard, which focuses exclusively on fixing issues related to the rendering of HTML5 content, the layout of several Web sites, and general stability. (Free updates; Safari 5.1: 47.47 MB; Safari 5.0.6: 52.51 MB)
Does Safari 5.1 require Snow Leopard 10.6.8 or only 10.6.5? The Apple pages are contradictory. I'm running 10.6.6 and I don't wish to upgrade.
Apple's site says 10.6.5 but it won't install on 10.6.7 saying it needs 10.6.8
Haven't read anything on Tidbits saying that the issues noted here on 10.6.8 had been fixed.
Safari 5.1 seems to have broken the LastPass extension. Also, Li'lSnitch complains about everything as coming from WebProcess. I may have to turn Li'lSnitch off.
Safari 5.1 has also broken 1Password.
Safari 5.1 broke one of my JavaScripts. It had worked in the previous version (and in all other browsers I tested it in). Still doesn't throw any errors in the Safari JS debugger; perhaps it's a change in the DOM. As far as I can tell, "document" now includes the area occupied by the scroll bars too -- which I think is a bug. Maybe related to the new full-screen mode? Anyway, developers beware.