Apple has seeded a beta version of Safari 5.1.2 to developers. The new software includes bug fixes for a PDF viewing bug in earlier versions of Safari.

Safari 5.1.2 fixes issues where PDFs in frames were not displayed in the browser. Please test this build with websites that display PDF documents inline such as banks and document management systems.

The beta is available for registered developers on OS X Lion, OS X Snow Leopard, and Windows. Apple asks developers to test the new Safari release against printing and mouse and keyboard interaction. The release notes are pasted after the break (thanks Mike!):

Safari 5.1.2 Update:
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.

Inline PDF Support

Safari 5.1.2 fixes issues where PDFs in frames were not displayed in the browser. Please test this build with websites that display PDF documents inline such as banks and document management systems. Please also test saving and using context menus with PDFs in frames.

Plug-Ins

Please test mouse and keyboard interaction in plug-ins with input fields. Printing

Please test printing web pages. Printing web pages to PDF is sufficient. Known Issues

There is a known issue with some Safari Extensions that use the ‘beforeload’ event. This can cause Safari to crash under certain circumstances.

Known Limitations

To uninstall this preview software on a Mac, download the uninstaller in the Mac Dev Center or the Safari Dev Center. You must be logged in to access the uninstaller.

To uninstall this preview software on a computer running Windows, go to “Control Panel” and then “Programs and Features,” select “Safari” and then click “Uninstall.”

page1image14032
page1image14304
page1image14576
page1image14848
page1image15120

APPLE CONFIDENTIAL

Bug Reporting

This build is being provided to you for testing and development purposes. Should you encounter any problems, please submit a bug report using the online Bug Reporter at http://bugreporter.apple.com/. Please make sure to include “Safari 5.1.2″ in the bug title and description. Please also include the build number in your description (in the Safari menu, select “About Safari”; the build number is available there in parentheses. For example, “Version 5.1.2 (7534.52)”) This information will help ensure that your bug is processed quickly.

When submitting a bug report, please make sure to include a Summary, Steps to Reproduce, Actual Results, Expected Results, the System Profile Report, and any other relevant information that is necessary to process the report. Please note if the bug is a regression from previously shipped version of the software.

When reporting bugs in Full Screen mode, please include the following information:

  1. Which bars are visible before entering full screen mode (address bar, bookmarksbar, extensions bars, tab bar, status bar)
  2. Which bars are always visible after entering full screen mode (address bar,bookmarks bar, tab bar, status bar)
  3. Was the menubar visible when the bug occurred?

IMPORTANT: Engineering requires additional information for crashing bugs, kernel panics, hanging issues, and WebKit on Windows bugs.

Crashing Bugs: Crash logs are required for crashing bugs. Crash logs can be located in ~/Library/Logs/CrashReporter. To learn how to obtain crash logs on Windows, see http://www.webkit.org/quality/crashlogs.html.

Kernel Panics: Backtraces, which contain vital information for investigating kernel panics, are required for kernel panic issues. Backtraces can be saved to nvram on restart shutdown, then copied to the panic.log file on restart. The panic.log file can be found in /Library/Logs/PanicReporter.

Hanging Issues: When an application is hung, a Sample should be provided. This can be done using the Activity Monitor (/Applications/Utilities/). To generate a Sample using this utility, click on the hung application name, then from the View Menu select “Sample Process.”

For complete instructions on submitting bug reports, please visit the Bug Reporting page at http://developer.apple.com/bugreporter/. Thank you for your support.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s