Subject: The Omni Group Releases OmniWeb 4.0.6

The Omni Group Releases OmniWeb 4.0.6
Ken Case Talks About 4.1 Release

Seattle, Washington — December 6, 2001 — Today, The Omni Group
released OmniWeb 4.0.6, the award winning native Cocoa web browser built
for Mac OS X. Major changes for OmniWeb 4.0.6 include compatibility
fixes with Mac OS X 10.1, newly added support for Norwegian, and support
for Simplified and Traditional Chinese. See below for complete release
notes.

In discussing the release of OmniWeb 4.0.6, Ken Case, Director of
Engineering, makes note of the delay in shipping OmniWeb 4.1. “We were
hoping to ship OmniWeb 4.1 by now, but ran into issues incorporating our
new JavaScript engine (it’s now based on the “SpiderMonkey” code from
Mozilla/Netscape). We decided that waiting and shipping a complete and
solid version of 4.1 was the best thing to do but in the meantime 4.0.6
fixes some key compatibility issues with Mac OS X 10.1.”

The Omni Group expects to ship OmniWeb 4.1 in time for Macworld, SF. Ken
Case notes, “With OmniWeb 4.1 you should see some major improvements in
compatibility and speed. Our goal is that OmniWeb can be your Mac OS X
browser of choice for 100% of the web sites you visit.”

Information about The Omni Group:

The Omni Group, founded in 1993, develops Mac OS X applications
including OmniWeb, OmniGraffle, and OmniOutliner; provides Mac OS X
based consulting services such as porting games to Mac OS X; and employs
20 unique individuals who really really want iPods for Christmas :).
Information on The Omni Group is available at http://www.omnigroup.com/.

– 4.0.6sp1
– Additional supported languages
– Norwegian
– Simplified Chinese
– Traditional Chinese
– 4.0.6rc1
– Fixed compatibility issues with Mac OS X 10.1
– OmniWeb crashes on quit (unless you reset your PRAM)
– Source code editing doesn’t work
– OmniWeb sometimes crashes when closing windows
– Font metrics aren’t correctly processed for some fonts
(notably Japanese fonts)
– Images are scaled based on source DPI, rather than being
displayed at pixel size
– Other fixes
– Security fix: OmniWeb auto-opens downloaded files, which can
be a security hazard (for example, this means that .jar files
get run automatically in 10.1)
– Implemented a new default,
OHDownloaderLaunchableApplications, which
defines the set of applications which we’re willing to
automatically
launch to present a downloaded file. By default the set
is empty, so
we do nothing when the download completes.
– When OmniWeb fails to parse some CSS, it doesn’t render the
page at all
– OmniWeb can’t be launched from a folder with a slash in it
– Switched to using @executable_path to reference internal
frameworks rather than defining a framework search path
– When Flash would try to read a file, we’d mistakenly treat
that as a request to display the file (replacing the current
page), causing problems at pages like www.espn.com
– 4.0.6
– Aborted images no longer stay broken when you try to load them
again quickly (which happens a lot on pages with rollovers, or
when quickly navigating a site)
– Fixed JavaScript crash when trying to change a select option’s
value to something we don’t support. This fixes the crash at
www.seagate.com.
– We once again strip line breaks from the middle of URLs in HTML,
fixing problems at a ton of web sites including amazon, yahoo,
and ebay