About Camino 1.1 Beta
Camino 1.1 Beta is a heavily-updated version of the only native Mac OS X browser using Mozilla.org’s Gecko HTML rendering engine. Notable improvements include enhanced tabbed browsing (“single window mode”), integration with the Mac OS X spell-checking system, detection of RSS/Atom feeds, an improved design for the “blocked pop-up” notification, enhanced options for cookies and downloads, and a resizable search field in the toolbar. This release also includes enhancements in speed, security, and rendering accuracy brought by version 1.8.1 of the Gecko rendering engine.
Note that Camino 1.1 Beta is in the “beta” stage, which means that it is close to its final shipping state. We feel that it is usable on a day-to-day basis and is a large improvement over Camino 1.0, but you may still experience bugs and some functionality may not work entirely as intended. The goal of this release is to demonstrate the team’s progress and to allow users to report problems before the final release.
Camino 1.1 Beta shares the same code base as Firefox 2.0, both being based on version 1.8.1 of Gecko, and thus shares many of the security fixes and Gecko improvements that are in that version of Firefox.
Features in Camino 1.1 Beta
The following changes and improvements have been made since the Camino 1.1 Alpha 2 release.
- Fixed a bug where the scrollbar would sometimes redraw incorrectly.
- Clicking on the feed icon in the location bar now works properly on sites using Internationalized Domain Names (IDNs).
- If Camino crashes, on the next launch it provides the option to restore the pages that were open prior to crashing.
- The site icon for local files now acts as a proxy for the file and behaves like the titlebar proxy icon in applications like TextEdit.
- “Force Reload” (Cmd-Shift-R) now forces a page’s site icon to be reloaded from the server as well.
- Fixed a bug in Camino 1.1a2 where icons in the Bookmarks Manager or the location bar for missing local files were sometimes displayed improperly.
- Renamed the "Keyword" field "Shortcut" to more accurately reflect its function.
- Added “Space” and “Separator” items to the list of toolbar elements for the Downloads window toolbar.
- Camino no longer hangs when downloading files to the Desktop with Quicksilver running.
- Restored the preference to disable plug-ins (which was removed in Camino 0.9).
- Camino now includes a preference to enable restoring of pages which were open when the user quit Camino.
- The “Pop-up Exceptions List” now includes the ability to allow or deny pop-up windows from specific sites.
Privacy & Security
- Camino now includes support for Kerberos authentication used in many internal networks.
- Camino now reads Safari keychain items that match with a generic port if no item that matches with a specific port is available.
- “Reset Camino…” now removes any passwords in the Keychain that were created or changed by Camino 1.1a2 or later.
- Camino now checks the “form action domain” before filling saved usernames and passwords from the Keychain and prompts the user if the “form action domain” does not match.
- When a website wants to show a pop-up window, the pop-up blocker now provides a choice of showing the pop-up once, showing pop-ups from the site automatically in the future, or preventing pop-ups from the site automatically.
- If a URL sent to Camino from an external application is already open, Camino will show the existing tab or window containing that URL instead of opening a new tab or window.
- Long page titles will now properly middle-truncate in the title bar.
- The hover state for the pop-up blocker’s close button now appears properly, and the button itself is now more visible.
Web Page Interaction
- Ad-blocking has been further improved.
- Camino no longer opens a new window or tab when the user Cmd-clicks a mailto: link.
- Camino now supports learning and ignoring words when checking spelling in web page text fields.
- Camino now includes support for “click-to-play” blocking of Flash animations (based on http://flashblock.mozdev.org).
Known Issues in Camino 1.1 Beta
- Some users report have reported that their bookmarks have disappeared when relaunching Camino and the Camino’s bookmarks backup file is corrupted. Users are advised to make regular copies of their bookmarks.
- Some users have experienced a situation where pages would appear not to load after clicking on a link. In this case, resizing the browser window will cause the page to display properly.
- The version of RealPlayer released in May 2006, version 10.1.0 (v400), 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) plugin causes major rendering issues in Camino. Since Microsoft has discontinued WMP on Mac OS X, Camino no longer supports the use of the WMP plugin; instead, all users should download the free Flip4Mac (F4M) plugin, version 2.1 or higher, from http://www.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 plugin.
- Due to a bug in Mac OS X 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 Camino user interface 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 manually, ensuring the Carbon versions of the font names are used.