Camino 1.0.5 Release Notes

Changes since Camino 1.0

The following changes and improvements have been made since the Camino 1.0 release.

In Camino 1.0.5, we have made the following changes and improvements since version 1.0.4:

Fixed several critical security and stability issues, including those fixed in version 1.8.0.12 of the Mozilla Gecko rendering engine.

Thumbnails at Picasa will now display properly.

On Mac OS X 10.2 and 10.3, Script Editor will no longer complain that it cannot open Camino’s AppleScript dictionary, and all AppleScripts that interact with Camino will work just as they do on Mac OS X 10.4.

Viewing the list of installed plug-ins will no longer cause disabled security warnings to appear when browsing.

When changing Chinese, Japanese, or Korean font preferences, using the “Advanced” sheet will now set the font correctly.

Camino now prompts the user before automatically filling a form with a saved username and password from the Keychain if the domain name that the form will be submitted to has changed since the password was saved.

Upgraded the bundled Java Embedding Plugin to version 0.9.6.2.

Further improved ad-blocking.

In Camino 1.0.4, we have made the following changes and improvements since version 1.0.3:

Fixed several critical security and stability issues, including those fixed in version 1.8.0.10 of the Mozilla Gecko rendering engine.

Sheets will now close as expected on Intel-based Macs.

Upgraded the bundled Java Embedding Plugin to version 0.9.6.

Added support for importing iCab 3 bookmarks.

Improved the handling of Internet Explorer .url shortcut files.

The text of certain security dialogs now contains “Camino” instead of “(null)”.

Camino will now make a backup copy of the bookmarks file when it launches if the file is not corrupt.

Camino will automatically restore bookmarks from a backup when it launches if they are unreadable.

Further improved ad-blocking.

In Camino 1.0.3, we have made the following changes and improvements since version 1.0.2:

Fixed several critical security and stability issues, including those fixed in version 1.8.0.7 of the Mozilla Gecko rendering engine.

Upgraded the bundled Java Embedding Plugin to version 0.9.5+g.

The “Reset Camino…” command will now reset minimized windows.

Fixed an issue where Cmd-B would fail to act as a toggle in some cases.

Further improved ad-blocking.

In Camino 1.0.2, we have made the following changes and improvements since version 1.0.1:

Fixed several critical security issues, including those fixed in version 1.8.0.4 of the Mozilla Gecko rendering engine.

Fixed an issue in Camino 1.0.1 where proxy auto-config (PAC) files were ignored.

Fixed an issue where Camino’s bookmark metadata could not be added to the list of locations Spotlight is prevented from searching.

Fixed an issue where using Camino on a network with many Bonjour hosts could significantly degrade performance.

Fixed an issue where Camino would ignore the “Link from other application” tabbed browsing preference in certain cases.

In Camino 1.0.1, we have made the following changes and improvements since version 1.0:

Fixed several critical security issues, including those fixed in version 1.8.0.3 of the Mozilla Gecko rendering engine.

Upgraded the bundled Java Embedding Plugin (http://javaplugin.sf.net) to version 0.9.5+d

Improved ad-blocking, especially of German ads

Enabled the opening of local SVG files

Fixed an issue where Camino on Intel-based Macs was unable to read Keychain entries stored by Camino on PowerPC-based Macs.

About Camino 1.0

Camino 1.0 brings you a heavily-updated version of the only native Mac OS X browser using Mozilla’s Gecko rendering engine. Thousands of bugs were fixed in Gecko 1.8, providing users with improved web page compatibility.

The features listed below are just some of the many in Camino 1.0.

Note: Due to major changes in Camino, Mac OS X 10.1 is no longer supported. Users still running Mac OS X 10.1 should continue to use Camino 0.8.5.

We want to know what you think! Be sure to contact us and let us know what you think.

What’s New in Camino 1.0

Camino 1.0 brings a heavily updated version of the only native Mac OS X browser using Mozilla.org’s Gecko HTML rendering engine (version 1.8), the same rendering engine used by the popular Firefox 1.5 web browser.

Here’s what’s new in Camino 1.0:

Universal Binary - Camino is now a universal binary, allowing it to run natively on both PowerPC- and Intel-based Macs.

Downloading Camino

Installing Camino

Installing Camino is as simple as copying the app to your Applications folder. Instructions can be found on the disk image.

Known issues

Camino 1.0.5 will fail to log in to most websites when running on Mac OS X 10.2.8. This issue was fixed in Camino 1.0.6.

RealPlayer version 10.1.0 (v400), released in May 2006, causes Camino to crash when viewing any Real content. Real has released RealPlayer 10.1.0 (v412) to address this issue. Users should re-download RealPlayer and verify (using the application’s About window) that it is version 412 before launching Camino.

Microsoft’s Windows Media Player (WMP) plug-in causes major rendering issues in Camino. Since Microsoft has discontinued WMP on Mac OS X, Camino no longer supports the use of the WMP plug-in; instead, all users should download the free Flip4Mac (F4M) plug-in, version 2.1 or higher, from flip4mac.com. Version 2.1 causes pages containing WMP content to become white when scrolled in Camino; there is currently no ETA for a fixed version of the F4M plug-in.

Although typing performance has improved in Camino 1.0, typing in form fields can be slow when Flash or animated images are present. Turning off animations can improve performance in some cases.

Shockwave Director content displays at the wrong location in the browser window when hardware rendering is enabled. Switch the plugin to software rendering to solve this.

Due to a bug in Mac OS X 10.2.x and 10.3.x, Norwegian users of Camino will need to manually set their 'accept-language' string. To set the accept-language string, add the string user_pref("camino.accept_languages", "nb,nn,no,en"); to your user.js file, where the languages are listed in the order in which you’d prefer them if a server can send content in multiple languages. (In this example, you want Bokmål first, then Nynorsk, then generic Norwegian, then English if none of the other three languages are available.) You may now launch Camino.

Apple fixed this bug in Mac OS X 10.4, so no work-arounds are necessary.

Camino erroneously claims that the default Japanese and Traditional Chinese fonts are “missing” when they are actually installed; this is due to a mismatch between Carbon and Cocoa font names. Changing these fonts using the Fonts preference pane will result in incorrect fonts being chosen and will cause some characters to fail to display. Users should either keep the default fonts or change the font preferences using the “Advanced…” sheet instead.

Some users have experienced an issue where downloading files will cause Camino to hang when Quicksilver is installed. Users can work around this issue by either disabling indexing of the Desktop in Quicksilver or by setting the default download location to somewhere other than the Desktop in Camino’s Downloads preferences.