Difference between revisions of "Releases:Release Notes 2.0"

From Camino Wiki
Jump to navigation Jump to search
(→‎Web Page Interaction: I guess this is really the last item)
(→‎General: oops)
 
(49 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 2.0b1 are at [[Releases:2.0b1:Notes]] (Release Notes for Camino 2.0a1 are at [[Releases:2.0a1: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.0b1.
+
These notes are for checkins after the release of Camino 2.0b4.
  
 
== General ==
 
== General ==
 +
* Viewing a full-screen Flash video no longer causes the keyboard shortcut for “Close Tab” to close the entire window instead.<!--or something-->
 +
* 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.-->
 +
* 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==
 
==Bookmarks & History==
* Added support for importing bookmarks from SeaMonkey 2.
+
* Exporting bookmarks using the Safari format no longer uses an incorrect filename extension on subsequent exports.<!--or something fun :P -->
* When the Top Ten List collection is used as the Dock menu, “Use as Dock menu” will be checked in the context menu.<!--bleh; we may want to drop this note-->
+
* Added support for importing Opera 10 bookmarks.
* Site icons in the bookmarks and history menus now display properly even when modifier keys are pressed.
 
* It is once again possible to move bookmarks that were imported from HTML-based bookmark files.<!--not sure how to qualify "via the HTML bookmarks importer" most sanely-->
 
* Bookmark folders expanded during bookmark dragging now auto-collapse after dropping the bookmark.<!--could be better-->
 
  
 
==Downloading==
 
==Downloading==
* If [http://www.growl.info/ Growl] is installed, Camino will generate notifications when downloads begin and finish.
 
  
 
==Localization==
 
==Localization==
  
 
==Preferences==
 
==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==
 
==Privacy & Security==
 +
* It is once again possible to trust new Certificate Authorities.
  
 
==Tabs==
 
==Tabs==
* On Mac OS X 10.4, background tabs will now draw properly while dragging.<!--regression/bug shipped in b1-->
+
* 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==
 
==User Interface==
* Non-ASCII characters in URLs are now displayed in a readable format in tooltips.
+
* 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==
 
==Web Page Interaction==
* Pop-up menu <code>&lt;select&gt;</code>s will always display using the Aqua appearance.<!--eh-->
 
* Improved ad-blocking.
 
* Upgraded the “Block flash animations” code to use Flashblock 1.5.8.
 
* Flash animations will no longer continue running once the page containing them has been closed.
 
  
 
==Known Issues==
 
==Known Issues==
''merge from [[Releases:2.0b1:Notes]] if needed''
+
''merge from [[Releases:2.0b4:Notes]] if needed''
 
* Need to bump Shockwave 11.0 to 11.0r470 to avoid {{bug|445520}}
 
* 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?

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?