The Omni Group has released OmniWeb 5.1 Beta 2. This updated Web browser includes improved debug logging and several other bug fixes in anticipation of the final OmniWeb 5.1 release. Like OmniWeb 5.1 Beta 1, this version sports an updated version of the WebCore HTML rendering engine found in Safari. From the release notes:

Highlights

• You can once again use the delete key to delete bookmarks and history entries.
• Fixed an issue that caused iOpen in New Tabsi menu items to be disabled.
• Corrected an issue with the Software Update mechanism.

Changes

• Fixed a number of memory leaks. This will probably introduce some new crashers, so please send in all of your crash reports so we can correct the issues ASAP.
• There is a new option in the contextual menu for the Error Log window that will enable debug logging for our internal scheduler. If you experience unexplained high CPU usage with this beta version, please do the following while OmniWeb is using a lot of processor time:
• Display the Error Log window (Window > Error Log)
• Clear the log using the button on the window.
• Enable the logging by right-clicking (or control-clicking) in the content area of the window, then choosing Debug Scheduler from the context menu.
• Let the logging happen for 5-10 seconds, then disable it by selecting the item from the context menu again.
• Copy and paste the output into an email message and send it to omniweb5@omnigroup.com or just use the Send Feedback function under the Help menu in OmniWeb.
• Fixed some cases where links and other URLs were not being parsed correctly (such as and .
• Fixed a thread-safety issue with plug-ins and a memory leak with text rendering.

OmniWeb 5.1 Beta 2 requires Mac OS X version 10.2 or higher. It is available at the OmniWeb beta download page.