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 this version 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 Gecko 1.8.1, 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 quits unexpectedly and is relaunched, it will provide the option to restore the pages that had previously been open.
- The site icon for local files now acts as a proxy for the file and behaves in accordance with Apple’s Human Interface Guidelines.
- “Force Reload” (Command-Shift-R) now forces a page’s site icon to be reloaded from the server as well.
- Icons for missing local files are now displayed properly in the location bar and the Bookmarks Manager.
- The “Keyword” field has been renamed “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 1.0.
- Added a preference to restore pages that were open when the user last 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 supports Kerberos authentication, most commonly seen on internal networks.
- Camino will use Keychain passwords saved without a port number if no password with a specific port is available. This improves compatibility with Keychain passwords stored by Safari.
- “Reset Camino…” now removes any passwords in the Keychain that were created by Camino 1.1a2 or later.
- 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.
- The pop-up blocker now provides the ability to show a pop-up once, show all future pop-ups from a site, or prevent the display of any future pop-ups from a site.
- If an external application tries to open a link in Camino, and it is already open, Camino will show the existing tab or window instead of opening a new one.
- Long pages titles will now properly display in the title bar with an ellipsis (…) in the middle.
- The pop-up blocker’s close button is shown with the correct appearance when the mouse pointer is over it, 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 command-clicks a mailto: link.
- Camino can now learn and ignore words when checking spelling in text fields in web pages.
- Camino now includes support for “click-to-play” blocking of Flash animations, based on FlashBlock from http://flashblock.mozdev.org/.
Known Issues in Camino 1.1 Beta
- Some users have reported losing their bookmarks when Camino’s bookmarks backup file becomes 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 may allow the page to display properly.
- 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) 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.