Difference between revisions of "Releases:1.5:Notes:Web"

From Camino Wiki
Jump to navigation Jump to search
(add [lnk] for places we'll want a link)
(→‎Known Issues in Camino 1.5: remove these 2 per sam/me)
Line 44: Line 44:
  
 
=Known Issues in Camino 1.5=
 
=Known Issues in Camino 1.5=
 
* 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.
 
* 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.
 
* 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 <tt>user_pref("camino.accept_languages", "nb,nn,no,en");</tt> to your [http://www.caminobrowser.org/support/hiddenprefs/#createUserjs 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.<br>Apple fixed this bug in Mac OS X 10.4, so no work-arounds are necessary.
+
* 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 <tt>user_pref("camino.accept_languages", "nb,nn,no,en");</tt> to your [http://www.caminobrowser.org/support/hiddenprefs/#createUserjs 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.<br>Apple fixed this bug in Mac OS X 10.4, so no work-arounds are necessary. {{greyText|this needs to be shortened here and moved to FAQ}}
  
 
* 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.
 
* 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.

Revision as of 13:35, 15 April 2007

* * * DRAFT * * *

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. Thousands of bugs were fixed in Gecko 1.8.1, providing users with improved web page compatibility.

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

Note: Due to major changes in Camino, Mac OS X 10.2 is no longer supported. Users still running Mac OS X 10.2.8 should continue to use Camino 1.0.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.5

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

Here are the highlights of what's new in Camino 1.5:

  • Improved tabbed browsing - Camino now supports forcing links that would open new windows into new tabs instead (“single-window mode”) and returning to the original page after viewing a page in a new tab (“tab jumpback”).
  • Spelling - 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 offer to pass it to the system’s default feed reading application.
  • Session saving - Camino can remember which pages were open when quitting and restore those pages when restarting. Camino will also offer to restore pages open before a crash.
  • Keychain compatibility - Camino can now read Keychain entries saved by Safari and can also share entries with Safari.
  • Pop-up blocking - The new, more noticeable pop-up notification also offers simplified options for showing and blocking pop-ups.
  • Plug-in blocking - Camino 1.5 now provides an option to disable all plugins and also includes the ability to block Flash animations until the user clicks on them (“Flashblock”).
  • Window zooming - The Zoom command now resizes the window to fit the current page’s content instead of making the window full-screen.
  • Downloading - A new optional toolbar icon in the Downloads window allows users to send the selected download to the trash. In addition, two new preferences were added: one to remove successfully completed downloads automatically and one to clear the download list upon quitting Camino.
  • Searching - The search field in the toolbar is now resizable.
  • Cookie management - Camino now support includes an option to accept cookies only for the current session.
  • JS 1.7 in Gecko (any other major Gecko features? or just zap this)

See the complete release notes [lnk] for a list of all changes from 1.0.5 to 1.1.

Downloading and Installing

System Requirements

Camino now requires Mac OS X 10.3 (users of 10.2 can download Camino 1.0.5 English [lnk] or Multilingual [lnk]). In addition, a minimum of 30 MB of free hard drive space and 128 MB of RAM is required.

Downloading Camino

You can download Camino from the main project page [lnk].

Installing Camino

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

Known Issues in Camino 1.5

  • 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.
  • 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. this needs to be shortened here and moved to FAQ
  • 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.