Focus Areas
Please focus testing on the following areas:
- General website compatibility
- Extension compatibility
- Debugging using Web Inspector
Known Issues
OS X El Capitan and OS X Yosemite
- Flash Player 18.0.0.232 does not work consistently with Safari’s tab audio feature. Adobe is aware of the problem and will fix it with a future update.
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 9.0.1 for El Capitan” or “Safari 9.0.1 for Yosemite” or “Safari 9.0.1 for Mavericks” in the bug title and description. Please also include the build number in your description. You may determine the build number by opening the Safari menu and selecting “About Safari”; the build number is available there in parentheses.
OS X El Capitan and OS X Yosemite
- Flash Player 18.0.0.232 does not work consistently with Safari’s tab audio feature. Adobe is aware of the problem and will fix it with a future update.
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 9.0.1 for El Capitan” or “Safari 9.0.1 for Yosemite” or “Safari 9.0.1 for Mavericks” in the bug title and description. Please also include the build number in your description. You may determine the build number by opening the Safari menu and selecting “About Safari”; the build number is available there in parentheses.
For example, “Safari 9.0.1 for Yosemite (10601.2.4)” or “Safari 9.0.1 for Mavericks (9537.86.2.4)”. This information will 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, sysdiagnose, 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. Attach a screenshot of the Safari window before entering Full Screen mode. (Cmd-Shift-4, space bar, click the highlighted Safari window. Window screenshot is saved to Desktop.)
2. Attach a screenshot of Safari in Full Screen mode. (Cmd-Shift-3. Screenshot saved to Desktop.)
3. Was the menubar visible when the bug occurred?
IMPORTANT: Engineering requires additional information for crashing bugs, kernel panics, and hanging issues.
Crashing Bugs: Crash logs are required for crashing bugs. Crash logs can be located in ~/Library/Logs/CrashReporter.
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."
Sysdiagnose: A sysdiagnose is very useful in diagnosing a number of issues. To collect a sysdiagnose for Safari, bring Safari to the foreground and press Control-Cmd-Option-Shift-Period.
For complete instructions on submitting bug reports, please visit the Bug Reporting page at http://developer.apple.com/bugreporter/. Thank you for your support.
When submitting a bug report, please make sure to include a Summary, Steps to Reproduce, Actual Results, Expected Results, the System Profile Report, sysdiagnose, 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. Attach a screenshot of the Safari window before entering Full Screen mode. (Cmd-Shift-4, space bar, click the highlighted Safari window. Window screenshot is saved to Desktop.)
2. Attach a screenshot of Safari in Full Screen mode. (Cmd-Shift-3. Screenshot saved to Desktop.)
3. Was the menubar visible when the bug occurred?
IMPORTANT: Engineering requires additional information for crashing bugs, kernel panics, and hanging issues.
Crashing Bugs: Crash logs are required for crashing bugs. Crash logs can be located in ~/Library/Logs/CrashReporter.
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."
Sysdiagnose: A sysdiagnose is very useful in diagnosing a number of issues. To collect a sysdiagnose for Safari, bring Safari to the foreground and press Control-Cmd-Option-Shift-Period.
For complete instructions on submitting bug reports, please visit the Bug Reporting page at http://developer.apple.com/bugreporter/. Thank you for your support.
Download:
- Yosemite: Uploading
- Mavericks: Uploading
Post A Comment:
0 comments: