Apparently, the website used Releases:1.5:Notes:Web format for the final 1.0 notes, while the Release Notes RTF used a different format :p
* * * DRAFT * * *
About Camino® 1.5
After over a year of hard work by devoted volunteers, the Camino Project is proud to give you Camino 1.5. This latest version fixes hundreds of bugs and implements many new features, providing all users with an improved browsing experience.
Camino 1.5 brings you a heavily updated version of the only native Mac OS X browser using Mozilla’s Gecko rendering engine. This release displays web pages with Gecko 1.8.1, the same rendering engine used by the popular Firefox 2 web browser. Gecko 1.8.1 includes thousands of bug fixes over the version used by Camino 1.0, providing users even better web page compatibility.
The features listed below are just some of the many changes in Camino 1.5.
Features in Camino 1.5
The following are the major changes and improvements made since the Camino 1.0 release. A full list is available on our website.
- Spell-checking using the Mac OS X spelling dictionaries is now enabled in web page text fields.
- Feed detection
- When a web page offers an Atom or RSS feed, Camino will detect the feed and can pass it to the system’s default feed reading application.
- Session restore
- Camino can remember which pages were open when quitting and restore them the next time it opens.
- After a browsing session has terminated unexpectedly, Camino will offer to restore the pages which were open previously.
- Improved tabbed browsing
- There is a new option to force links that would open new windows into new tabs instead (“single-window mode”).
- Camino now supports returning to the original tab after viewing a page in a new tab (“tab jumpback”).
- Keychain compatibility
- Camino can now share Keychain entries with Safari.
- Keychain entries saved by Camino are now saved in a way that allows other applications to read them.
- Pop-up blocking
- The pop-up blocking notification is now more visible.
- The new pop-up notification offers more powerful controls for managing pop-ups.
- Enhanced plug-in control
- Camino 1.5 includes the ability to disable all plug-ins.
- The new “Block Flash animations” option prevents Flash from starting until the user clicks play (“Flashblock”).
- Window zooming
- The Zoom command now resizes the window to fit the current page’s content instead of making the window full-screen.
- A new optional toolbar icon in the Downloads window allows users to move downloaded files to the Trash.
- Items in the Downloads window can now be automatically removed upon completion or when quitting Camino.
- The search field in the toolbar is now resizable.
- The context menu for selected text in web pages now includes a “Search” item.
- Cookie management
- Camino now includes an option to accept cookies only for the current session.
- User interface polish
- Camino 1.5 includes a major reorganization of menus and keyboard shortcuts and redesigned preference panes.
- Web content
For information about other issues or problems, please visit our Help page [lnk].
- 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.
- 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.
- 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.