About Camino 1.0 Release Candidate 1
Thank you for downloading Camino 1.0 Release Candidate 1. This is not the final version of Camino 1.0. It is a high-quality pre-release that demonstrates what we expect to release as Camino 1.0 shortly. This latest version fixes hundreds of bugs and implements many new features, providing all users with an improved browsing experience.
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.4.

Features in Camino 1.0
Below is a list of the major changes in Camino 1.0. A full list is available on our website.
	•	General
	•	Camino is now a universal binary, allowing it to run natively on both PowerPC- and Intel-based Macs.
	•	Moving backward and forward through history is now “blazingly fast”.
	•	The “Fill Form” menu item and toolbar button use your personal Address Book card to automatically fill out forms on the current webpage.
	•	Ad-blocking is now built-in, but turned off by default.
	•	The “Camino” menu now has a “Reset Camino…” menu item, which will erase your browsing history, empty the cache, clear downloads, clear all cookies, and clear all site permissions.
	•	The “Camino” menu now has an “Empty Cache…” menu item.
	•	An optional warning is shown when closing windows with multiple tabs or when quitting with multiple windows open.
	•	Camino now has certificate-management capabilities.
	•	It is now possible to trust a new Certificate Authority.
	•	The Certificates window, accessible from the Security preference pane, shows the set of certificates included with Camino and any newly-downloaded certificates.
	•	The about:config preference editor is now mostly functional.
	•	Bookmarks and History
	•	Camino now includes live searching of bookmarks and history.
	•	It is now possible to sort bookmarks alphabetically.
	•	The “Go” menu now displays global history, showing sites you visited in any window, ordered by date.
	•	Spotlight will now index Camino bookmarks.
	•	Camino now displays custom icons for Bookmarks, History, and local files.
	•	Tabbed browsing
	•	The tab bar has been rewritten from scratch.
	•	Tabs now appear on the left of the window, instead of in the center.
	•	Windows can now contain more than 16 tabs, and tabs which do not fit on the tab bar appear in an overflow menu.
	•	The tab bar can remain visible when a single tab is open.
	•	Double-clicking on empty space in the tab bar creates a new tab.
	•	Command-enter in the location bar or search field will now open the page or search results in a new tab or new window (instead of the current tab or window). 
	•	Downloading
	•	Camino now saves the list of downloads between sessions. 
	•	Downloads can be paused and resumed.
	•	Web Content
	•	Camino now has support for “document.designMode” (inline HTML editing, also known as Midas), SVG, the <canvas> tag, and MathML.
	•	Web page access keys now work in Camino.
	•	Camino now uses version 1.8 of Mozilla’s Gecko rendering engine, which contains thousands of bug fixes.
	•	Images are drawn and tiled using Core Graphics for improved performance.
	•	The pop-up blocker can now stop pop-ups generated by plugins (like Flash).
	•	Plugins
	•	Camino now ships with the Java Embedding Plugin (http://javaplugin.sourceforge.net/), which provides support for Java 1.4. On Mac OS X 10.4, Java 5.0 is also supported.
	•	Preferences
	•	Camino now supports third-party preference panes. These can be installed by placing them into the ~/Library/Application Support/Camino/PreferencePanes folder.
	•	There is a new preference to make animated images play only once.
	•	The cookie and cookie exception lists are now searchable.
	•	Camino now uses the language information in the International pane of the System Preferences to send data on what languages you understand to websites. This can be overridden by the "camino.accept_languages" hidden preference.
	•	Proxy Auto-Config (PAC) settings are now read from the entries in the Network pane of the System Preferences.

Known Issues
	•	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.0.1 or higher, from http://www.flip4mac.com/.  Version 2.0.1 displays some WMP content off-center in Camino; this will be fixed in the next maintenance release of the F4M plugin.
	•	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 hardwre 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 the Camino Multilingual edition will need to manually select their desired user interface language and manually set their 'accept-language' string. To make Camino Multilingual run in Nynorsk or Bokmål, select Camino Multilingual in the Finder and choose "Get Info" from the File menu. In the resulting window, click the triangle next to "Languages:" and uncheck every language except the one desired as Camino's UI language.
		To set the accept-language string, add the string user_pref("camino.accept_languages", "nb,nn,no,en"); to your [http://www-stage.caminobrowser.org/support/hiddenprefs/ 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.