Difference between revisions of "Releases:Release Notes 2.0"

From Camino Wiki
Jump to navigation Jump to search
(→‎General: add a 10.4 requirement)
(→‎General: oops)
 
(85 intermediate revisions by 2 users not shown)
Line 1: Line 1:
These are the “running” or incremental release notes for Camino 2.0 (<s>✈</s>), i.e., the interesting bug-fixes since the last major release (e.g., 1.5) or milestone (e.g., Camino 1.6 Alpha 1).  The actual release notes for major releases, milestones, or security releases can be found on the corresponding Releases:Ver:Notes page, e.g., [[Releases:1.6b1:Notes]].   
+
These are the “running” or incremental release notes for Camino 2.0 (), i.e., the interesting bug-fixes since the last major release (e.g., 1.5) or milestone (e.g., Camino 1.6 Alpha 1).  The actual release notes for major releases, milestones, or security releases can be found on the corresponding Releases:Ver:Notes page, e.g., [[Releases:1.6b1:Notes]].   
  
 
: (Note that not all checkins are considered interesting; in particular, fixes for regressions that only occur between milestones, code cleanup, or build changes are not included in release notes.)
 
: (Note that not all checkins are considered interesting; in particular, fixes for regressions that only occur between milestones, code cleanup, or build changes are not included in release notes.)
Line 7: Line 7:
 
These running release notes (and the milestone release notes that are developed from them) form the "complete" changelog on the website ([http://www.caminobrowser.org/releases/1.0/complete.php 1.0],  [http://www.caminobrowser.org/releases/1.5/complete.php 1.5]); the release notes for the final 2.0 release are a summary or short-form and can be found at [[Releases:2.0:Notes]].  
 
These running release notes (and the milestone release notes that are developed from them) form the "complete" changelog on the website ([http://www.caminobrowser.org/releases/1.0/complete.php 1.0],  [http://www.caminobrowser.org/releases/1.5/complete.php 1.5]); the release notes for the final 2.0 release are a summary or short-form and can be found at [[Releases:2.0:Notes]].  
  
<!--Release Notes for Camino 1.6b4 are at [[Releases:1.6b4:Notes]] (Release Notes for Camino 1.6b3 are at [[Releases:1.6b3:Notes]], notes for Camino 1.6b2 are at [[Releases:1.6b2:Notes]], notes for Camino 1.6b1 are at [[Releases:1.6b1:Notes]], and notes for Camino 1.6a1 are at [[Releases:1.6a1:Notes]]). -->
+
Release Notes for Camino 2.0b4 are at [[Releases:2.0b4:Notes]] (Release Notes for Camino 2.0b3 are at [[Releases:2.0b3:Notes]], notes for Camino 2.0b2 are at [[Releases:2.0b2:Notes]], notes for Camino 2.0b1 are at [[Releases:2.0b1:Notes]], and notes for Camino 2.0a1 are at [[Releases:2.0a1:Notes]]).
  
These notes are for checkins after the release of Camino 1.6.
+
These notes are for checkins after the release of Camino 2.0b4.
  
 
== General ==
 
== General ==
* Camino 2.0 Alpha 1 requires Mac OS X 10.4 or higher.
+
* Viewing a full-screen Flash video no longer causes the keyboard shortcut for “Close Tab” to close the entire window instead.<!--or something-->
* Uses version 1.9 of the Mozilla Gecko rendering engine, which includes a new graphics architecture based on Quartz and delivers improved compatibility with popular plug-ins and improved support for fonts and languages.<!--the fonts bit maybe could go-->
+
* Worked around a Flash bug to prevent Flash from crashing Camino when invoking Exposé while a Flash video is playing in full-screen mode.<!-- :P  or  Camino now prevents Flash from crashing invoking Exposé while a Flash video is playing in full-screen mode.-->
* Upgraded to version 1.5b6 of the Sparkle software update framework.
+
* Restored the ability to use the Delete key as a shortcut for “Back” and the Escape key as a shortcut to stop animated GIF files.
* The History menu now contains a sub-menu listing the last 20 closed web pages.
+
* Upgraded the built-in Growl framework to prevent Growl registration from stealing focus from Camino on Mac OS X 10.6.
  
==Bookmarks==
+
==Bookmarks & History==
* Added a page translation bookmarklet to default bookmarks.
+
* Exporting bookmarks using the Safari format no longer uses an incorrect filename extension on subsequent exports.<!--or something fun :P -->
* Dropping a bookmark on a collection no longer switches the active collection.
+
* Added support for importing Opera 10 bookmarks.
* The Bookmark Bar now accepts more drags as valid URLs by stripping control characters where necessary.<!--eh-->  
 
* It is now possible to drag plain-text <code>javascript://</code> URLs, such as bookmarklets, to the Bookmark Bar.
 
* The importer for HTML bookmark files has been completely rewritten and supports more HTML bookmark formats.
 
* The new HTML bookmark importer includes better support for bookmark attributes and for exported Firefox 3 bookmarks.
 
  
 
==Downloading==
 
==Downloading==
  
 
==Localization==
 
==Localization==
<!--hopefully we'll have Localize Gecko strings-->
+
 
 
==Preferences==
 
==Preferences==
* Changes to the font preferences now apply automatically.<!--eh-->
+
* Command-click now defaults to opening links in new tabs instead of new windows.
* Changes to the Home Page field in the General preference pane now apply without switching panes or closing the Preferences window.<!--bleh-->
+
* When adding cookie exceptions, Camino now adds the correct exception for “.sitename.tld” cookies.
 +
* The presence of non-ASCII data in cookie values no longer prevents display of the list of stored cookies.
  
 
==Privacy & Security==
 
==Privacy & Security==
* Camino now displays error pages for secure web pages using invalid or untrusted certificates.
+
* It is once again possible to trust new Certificate Authorities.
* Camino now supports adding exceptions to allow access to secure web pages whose certificates are invalid or untrusted.
 
  
 
==Tabs==
 
==Tabs==
* The Tab Overview feature displays a grid of thumbnails of the tabs in the current window.<!--bleh-->
+
* Added AppleScript support for setting the active tab in each browser window.
* Tab titles are now accessible to VoiceOver.
+
* Tabs now support “name” as an alias for the “title” property.
* The tab bar is now keyboard accessible.
 
* The Command-T keyboard shortcut is now always enabled and will create a new tab in the frontmost browser window.
 
  
 
==User Interface==
 
==User Interface==
* Control characters are now converted to spaces when pasting into the toolbar search field.
+
* Polished a number of Preferences and Downloads window toolbar icons to fit more closely with the visual style of Mac OS X 10.5 and later.
* Camino now intelligently strips control characters or converts them to spaces when pasting text into the location bar.
 
* Items in autocomplete lists no longer become editable on Mac OS X 10.5.
 
* Icons in the location bar no longer show the text cursor when mousing over them.<!--eh-->
 
* The location bar autocomplete list now displays the site icon for each web page.
 
* Directory listings on local disks and FTP sites have a more pleasing appearance.
 
* Clicking on a bookmarklet no longer changes the URL in the location bar.<!--this needs love-->
 
* Site icons in the location bar are now updated in more cases when changing tabs.<!--ugh-->
 
* The blocked pop-up notification bar is now keyboard accessible.
 
* It is now possible to tab into and out of the Find bar.
 
* The browser window now has a complete keyboard loop.
 
* The “Last Visited” column in the History is no longer editable.
 
  
 
==Web Page Interaction==
 
==Web Page Interaction==
* Web page form controls now better respect author styling.
 
* Camino now has support for making the entire content of a web page bigger or smaller.
 
* Improved ad-blocking.
 
  
 
==Known Issues==
 
==Known Issues==
 +
''merge from [[Releases:2.0b4:Notes]] if needed''
 +
* Need to bump Shockwave 11.0 to 11.0r470 to avoid {{bug|445520}}
 +
* Add Google Desktop crash note
 +
* Remove 1Password?
 +
* Reword Flash note to make it clear up-front that it's a Flash 9 plugin bug.
  
* Camino now requires Shockwave Player 11 or newer. <!-- not sure where to put this -->
+
General thought: can we break out the plugin bugs that have nothing to do with Camino 2 vs 1.6.x and label them differently? Bloggers using our release notes as their material sometimes call these out as if they are regressions.
* Delete no longer functions as a shortcut for Back.
+
: I wonder if we could have an item "Issues caused by incompatible third-party software" (or the like) and have the plug-in and hack issues be children of that item?
* Scrollbars appear active at all times.
 
* If “Ask me before accepting each cookie” is checked, Camino will display a cookie dialog for each cookie request from a web page.
 
* Include updated KIs from 1.6.4.
 

Latest revision as of 19:15, 10 November 2009

These are the “running” or incremental release notes for Camino 2.0 (☢), i.e., the interesting bug-fixes since the last major release (e.g., 1.5) or milestone (e.g., Camino 1.6 Alpha 1). The actual release notes for major releases, milestones, or security releases can be found on the corresponding Releases:Ver:Notes page, e.g., Releases:1.6b1:Notes.

(Note that not all checkins are considered interesting; in particular, fixes for regressions that only occur between milestones, code cleanup, or build changes are not included in release notes.)
There are several pages that track "major" changes on the trunk. These could be useful when we create our final release notes. What's new on the trunk for Firefox 3.

These running release notes (and the milestone release notes that are developed from them) form the "complete" changelog on the website (1.0, 1.5); the release notes for the final 2.0 release are a summary or short-form and can be found at Releases:2.0:Notes.

Release Notes for Camino 2.0b4 are at Releases:2.0b4:Notes (Release Notes for Camino 2.0b3 are at Releases:2.0b3:Notes, notes for Camino 2.0b2 are at Releases:2.0b2:Notes, notes for Camino 2.0b1 are at Releases:2.0b1:Notes, and notes for Camino 2.0a1 are at Releases:2.0a1:Notes).

These notes are for checkins after the release of Camino 2.0b4.

General

  • Viewing a full-screen Flash video no longer causes the keyboard shortcut for “Close Tab” to close the entire window instead.
  • Worked around a Flash bug to prevent Flash from crashing Camino when invoking Exposé while a Flash video is playing in full-screen mode.
  • Restored the ability to use the Delete key as a shortcut for “Back” and the Escape key as a shortcut to stop animated GIF files.
  • Upgraded the built-in Growl framework to prevent Growl registration from stealing focus from Camino on Mac OS X 10.6.

Bookmarks & History

  • Exporting bookmarks using the Safari format no longer uses an incorrect filename extension on subsequent exports.
  • Added support for importing Opera 10 bookmarks.

Downloading

Localization

Preferences

  • Command-click now defaults to opening links in new tabs instead of new windows.
  • When adding cookie exceptions, Camino now adds the correct exception for “.sitename.tld” cookies.
  • The presence of non-ASCII data in cookie values no longer prevents display of the list of stored cookies.

Privacy & Security

  • It is once again possible to trust new Certificate Authorities.

Tabs

  • Added AppleScript support for setting the active tab in each browser window.
  • Tabs now support “name” as an alias for the “title” property.

User Interface

  • Polished a number of Preferences and Downloads window toolbar icons to fit more closely with the visual style of Mac OS X 10.5 and later.

Web Page Interaction

Known Issues

merge from Releases:2.0b4:Notes if needed

  • Need to bump Shockwave 11.0 to 11.0r470 to avoid Bug 445520
  • Add Google Desktop crash note
  • Remove 1Password?
  • Reword Flash note to make it clear up-front that it's a Flash 9 plugin bug.

General thought: can we break out the plugin bugs that have nothing to do with Camino 2 vs 1.6.x and label them differently? Bloggers using our release notes as their material sometimes call these out as if they are regressions.

I wonder if we could have an item "Issues caused by incompatible third-party software" (or the like) and have the plug-in and hack issues be children of that item?