Earlier this month Apple seeded the first beta versions of Safari 7.1 (for Mavericks) and 6.2 (for Mountain Lion) to developers. Tonight a second beta has been published. Interestingly, aside from the focus areas outlined with the previous beta, Apple is also requesting that developers taking this beta for a spin try out the password and credit card auto-fill feature.
The 7.1 and 6.2 updates are expected to be the last big updates to those specific versions of Apple’s browser before the release of OS X Yosemite, which ships with Safari 8. The 7.1/6.2 update features big changes to the WebKit engine and extensions systems built into Safari. You can find the full seed notes for this beta below:
Safari 7.1 and 6.2 Beta 2:
Safari and WebKit Release Notes
Important: This is a preliminary document for an API or technology in development. Although this document has been reviewed for technical accuracy, it is not final. Apple is supplying this information to help you plan for the adoption of the technologies and programming interfaces described herein. This information is subject to change, and software implemented according to this document should be tested with final software and final documentation.
This beta build is not fully localized.
Safari 7.1 for OS X Mavericks requires OS X 10.9.4. Safari 6.2 for OS X Mountain Lion requires OS X 10.8.5.
Please focus testing on the following areas:
• Please test password and credit card AutoFill.
• Please test general website compatibility.
• Subpixel rendering is now on by default for all web content. Web sites or in-app web views with extremely tight design constraints may render differently.
• CSS object model getters will return fractional double values based on subpixel layout and rendering metrics instead of rounded integral values.
• Please test extension compatibility.
New WebKit Features
• WebGL. Safari support for WebGL allows developers to create 3D experiences that work natively without plug-ins.
• IndexedDB. The IndexedDB API allows web developers to store structured data for web applications that work online or require large amounts of data to be cached client side.
• CSS Shapes and Compositing. Using CSS, websites can now easily flow text around images and geometry shapes, and perform image compositing operations on DOM elements.
Thanks for the tip, Jean-Baptiste!