This includes the Chrome 16 release notes.

chrome/common/extensions/docs/static/whats_new.html

 <div id="pageData-name" class="pageData">What's New in Extensions?</div>
 <!-- <div id="pageData-showTOC" class="pageData">true</div> -->
 
 <p>
 This page lists the API and manifest changes
 made in recent releases.
 </p>
 
 <ul>
+  <li> <a href="#16">Google Chrome 16</a> </li>
   <li> <a href="#15">Google Chrome 15</a> </li>
   <li> <a href="#14">Google Chrome 14</a> </li>
   <li> <a href="#13">Google Chrome 13</a> </li>
   <li> <a href="#12">Google Chrome 12</a> </li>
   <li> <a href="#11">Google Chrome 11</a> </li>
   <li> <a href="#10">Google Chrome 10</a> </li>
   <li> <a href="#9">Google Chrome 9</a> </li>
   <li> <a href="#8">Google Chrome 8</a> </li>
   <li> <a href="#7">Google Chrome 7</a> </li>
   <li> <a href="#6">Google Chrome 6</a> </li>
 </ul>
 
 <p>
 In addition to the changes listed below,
 check out the
 <a href="experimental.html">experimental APIs</a>.
 </p>
 
+<h2 id="16"> Google Chrome 16 </h2>
+
+<h4> New APIs </h4>
+  <ul>
+    <li> The new
+      <a href="webNavigation.html">webNavigation API</a>

[kathyw, 2011/11/30 21:46:15]

I haven't been consistent about this, but I think it's best to use an English
name for the API. (The optional permissions API is the one that's convincing me
of this. :) So:

-> "web navigation API"

[mkearney, 2011/11/30 23:39:51]

Done.

+      lets extensions receive notifications about the status
+      of navigation requests.
+      This status can be tracked using navigation events.
+      For example,
+      the following navigation events are fired
+      at different stages in the completion of a web request:
+      <code>onBeforeNavigate</code>,
+      <code>onCommittedonDOMContentLoaded</code>,
+      and <code>onCompleted</code>.
+      
+    </li>
+    <li> The new
+      <a href="permissions.html">optional permissions API</a>
+      lets you control when users are presented with permission requests.
+      This ensures your users are not burdened with unnecessary permissions
+      and enables your users to understand the context of these permissions.
+    </li>
+    <li> The new
+      <a href="contentSettings.html">contentSettings API</a>

[kathyw, 2011/11/30 21:46:15]

contentSettings -> content settings

[mkearney, 2011/11/30 23:39:51]

Done.

+      lets extensions customize Chrome’s behavior
+      on a per-site basis instead of globally.
+      You can use this API to control whether websites can use features
+      such as cookies, JavaScript, and plug-ins.
+      </li>
+  </ul>
+
+<h4> Manifest changes </h4>
+  <ul>
+    <li> The new
+      <a href="manifest.html">requirements</a> field

[kathyw, 2011/11/30 21:46:15]

This item isn't very helpful. We should either delete it for now or give a more
specific link and/or rewrite this to be more informative. Perhaps add a little
example, such as:

For example, you might use this field to specify that your app requires Web GL.

[or whatever makes sense instead of "Web GL"]

[mkearney, 2011/11/30 23:39:51]

I chose to keep this in for the short term until we hear back from developers
about whether or not we need to document it. If we don't hear back, I will just
delete the whole thing, but for now, I figure no harm in giving it an extra day
or two. 

Also, I reworded it a little bit and included example.

On 2011/11/30 21:46:15, kathyw wrote:

+      allows you to declare extension requirements up front
+      so that your users can be informed of these requirements
+      before installing your extension.
+    </li>
+  </ul>
+  
+<h4> Additions to existing APIs </h4>
+  <ul>
+    <li> The new 
+    <a href="tabs.html#method-query">chrome.tabs.query()</a> method
+    gets all tabs that have the specified properties or
+    all tabs if no properties are specified.
+    This method has replaced the deprecated methods

[kathyw, 2011/11/30 21:46:15]

I'd delete the second sentence, since the deprecation is already covered by
another item.

[mkearney, 2011/11/30 23:39:51]

Done.

+    <code>chrome.tabs.getAllInWindow()</code> and
+    <code>chrome.tabs.getSelected</code>.
+    </li>
+    <li>The new
+    <a href="tabs.html#method-reload">chrome.tabs.reload()</a> method
+    reloads a tab and includes the option
+    to preserve the local cache of the reloaded tab.
+    </li>
+    <li>The management API's
+    <a href="management.html#type-ExtensionInfo">ExtensionInfo</a> object
+    now has an <code>updateURL</code> property.
+    </li>
+    <li>
+    You can now specify the supported locales for an external extension

[kathyw, 2011/11/30 21:46:15]

specify -> limit?

(that way it's clear that this is optional and just restricts locales)

[mkearney, 2011/11/30 23:39:51]

Done.

+    by adding the <code>supported_locales</code> attribute(s)

[kathyw, 2011/11/30 21:46:15]

Remove "(s)". We try to avoid it, and I'm pretty sure singular is good (or good
enough) here.

Add a link to where this is documented. Maybe:

an <a href="external_extensions.html">external extension</a>

[By the way... if you search for "supported_locale" in that page, you can see
that it's misspelled once, and the whole paragraph could use a copyedit. Oops.]

[mkearney, 2011/11/30 23:39:51]

I've implemented your changes. Also, I added to the top of my to-do list to
revise the external_extensions.html page.

On 2011/11/30 21:46:15, kathyw wrote:

+    to the <code>external_extensions.json</code>.
+    If your external extension supports all locales,
+    simply leave out this attribute.

[kathyw, 2011/11/30 21:46:15]

I'd delete this sentence. Save it for the real docs.

[mkearney, 2011/11/30 23:39:51]

Done.

+    </li>
+  </ul>
+  
+<h4> Changes to existing APIs </h4>
+  <ul>
+    <li>The methods <code>getAllInWindow</code> and

[kathyw, 2011/11/30 21:46:15]

getAllInWindow -> getAllInWindow()

(use () after method names)

[mkearney, 2011/11/30 23:39:51]

Done.

+    <code>getSelected</code> have been deprecated.

[kathyw, 2011/11/30 21:46:15]

getSelected -> getSelected()

[mkearney, 2011/11/30 23:39:51]

Done.

+    To get details about all tabs in the specified window, use
+    <a href="tabs.html#method-query">chrome.tabs.query {‘windowId’: windowID}</a>.

[kathyw, 2011/11/30 21:46:15]

This isn't standard syntax. How about:

<a href="tabs.html#method-query">chrome.tabs.query()</a> with the argument
<code>{‘windowId’: windowID}</code>.

also,  change the curly quote to straight quotes.

[mkearney, 2011/11/30 23:39:51]

Done.

+    To get the tab that is selected in the specified window, use
+    <a href="tabs.html#method-query">chrome.tabs.query {‘active’: true}</a>.

[kathyw, 2011/11/30 21:46:15]

Same change as the previous one, perhaps without the link.

[mkearney, 2011/11/30 23:39:51]

Done.

+    </li>
+    <li> You are no longer required
+    to specify the <code>tabID</code> for the
+    <a href="tabs.html#method-update">chrome.tabs.update()</a> method.
+    When not provided,
+    the <code>tabID</code> defaults to the selected tab of the current window.
+    </li>
+    <li>
+    External extension files on Mac OS can now be owned by users
+    within a wheel group (or an admin group).
+    </li>
+    <li>
+    The “experimental” permission is no longer required

[kathyw, 2011/11/30 21:46:15]

Change to straight quotes. We usually use straight quotes even where curly
quotes might be correct.

[mkearney, 2011/11/30 23:39:51]

Done.

+    for the
+    <a href="windows.html#type-Window">window “panel”</a> type.

[kathyw, 2011/11/30 21:46:15]

Again, change to straight quotes.

[mkearney, 2011/11/30 23:39:51]

Done.

+    By default, the “panel’ type creates a popup

[kathyw, 2011/11/30 21:46:15]

change to straight double-quotes.

(currently, they're curly and mismatched)

[mkearney, 2011/11/30 23:39:51]

Done.

+    unless the <code>--enable-panels</code> flag is set.
+    </li>
+  </ul>
+
 <h2 id="15"> Google Chrome 15 </h2>
 
 <p>Chrome 15 had a few minor API additions. Also see the Chrome Web Store’s new
 <a href="http://code.google.com/chrome/webstore/docs/inline_installation.html">inline
 installation</a> feature, which lets your website help users install extensions
 (and apps) without sending them away to the store.</p>
 
 <h4> Manifest changes </h4>
   <ul>
     <li> The new
@@ skipping 327 matching lines @@
   <ul>
     <li>The <a href="manifest.html#geolocation">geolocation</a> permission
       gives an extension access to the user's physical location. </li>
     <li><a href="match_patterns.html">Match patterns</a> can now select all
       schemes or all URLs. </li>
     <li>Access to file:/// URLs no longer triggers the "access to your machine"
       security warning, but now requires user opt-in from the extensions
       management page. </li>
   </ul>