This includes the Chrome 16 release notes.

It also includes updates to the manifest doc
to include the requirements field
which the release notes reference.

Review URL: http://codereview.chromium.org/8743020

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@114051 0039d316-1c4b-4281-b951-d872f2087c98

4 files changed, 253 insertions, 0 deletions

diff --git a/chrome/common/extensions/docs/manifest.html b/chrome/common/extensions/docs/manifest.html
index 2eb7700..4dbd5fe 100644
--- a/chrome/common/extensions/docs/manifest.html
+++ b/chrome/common/extensions/docs/manifest.html
@@ -337,6 +337,8 @@
                 </li><li>
                   <a href="#permissions">permissions</a>
                 </li><li>
+                  <a href="#requirements">requirements</a>
+                </li><li>
                   <a href="#version">version</a>
                 </li><li>
                   <a href="#manifest_version">manifest_version</a>
@@ -414,6 +416,7 @@ are <b>name</b> and <b>version</b>.
   "<a href="options.html">options_page</a>": "<em>aFile</em>.html",
   "<a href="#permissions">permissions</a>": [...],
   "<a href="npapi.html">plugins</a>": [...],
+  "<a href="#requirements">requirements</a>": {...},
   "<a href="autoupdate.html">update_url</a>": "http://<em>path/to/updateInfo</em>.xml"
 }
 </pre>
@@ -979,6 +982,41 @@ table.
 
 </tbody></table>
 
+<h3 id="requirements">requirements</h3>
+
+<p>
+Technologies required by the app or extension.
+Hosting sites such as the Chrome Web Store may use this list
+to dissuade users from installing apps or extensions
+that will not work on their computer.
+</p>
+
+<p>
+The only supported requirement is "3D",
+which denotes GPU hardware acceleration.
+For that requirement,
+you can list the 3D-related features your app requires,
+as demonstrated in the following example:
+</p>
+
+<pre>"requirements": {
+  "3D": {
+    "features": ["css3d", "webgl"]
+  }
+}
+</pre>
+
+<p>
+The "css3d" requirement refers to the
+<a href="http://www.w3.org/TR/css3-3d-transforms/">CSS 3D Transforms specification</a>,
+and the "webgl" requirement refers to the
+<a href="http://www.khronos.org/webgl/">WebGL API</a>.
+For more information on Chrome 3D graphics support,
+see the help article on
+<a href="http://www.google.com/support/chrome/bin/answer.py?answer=1220892">WebGL and 3D graphics</a>.
+Support for additional requirements checks may be added in the future.
+</p>
+
 
 <h3 id="version">version</h3>
 
diff --git a/chrome/common/extensions/docs/static/manifest.html b/chrome/common/extensions/docs/static/manifest.html
index af594a5..2fc6a02 100644
--- a/chrome/common/extensions/docs/static/manifest.html
+++ b/chrome/common/extensions/docs/static/manifest.html
@@ -51,6 +51,7 @@ are <b>name</b> and <b>version</b>.
   "<a href="options.html">options_page</a>": "<em>aFile</em>.html",
   "<a href="#permissions">permissions</a>": [...],
   "<a href="npapi.html">plugins</a>": [...],
+  "<a href="#requirements">requirements</a>": {...},
   "<a href="autoupdate.html">update_url</a>": "http://<em>path/to/updateInfo</em>.xml"
 }
 </pre>
@@ -620,6 +621,42 @@ table.
 </tr>
 </table>
 
+<h3 id="requirements">requirements</h3>
+
+<p>
+Technologies required by the app or extension.
+Hosting sites such as the Chrome Web Store may use this list
+to dissuade users from installing apps or extensions
+that will not work on their computer.
+</p>
+
+<p>
+The only supported requirement is "3D",
+which denotes GPU hardware acceleration.
+For that requirement,
+you can list the 3D-related features your app requires,
+as demonstrated in the following example:
+</p>
+
+<pre>
+"requirements": {
+  "3D": {
+    "features": ["css3d", "webgl"]
+  }
+}
+</pre>
+
+<p>
+The "css3d" requirement refers to the
+<a href="http://www.w3.org/TR/css3-3d-transforms/">CSS 3D Transforms specification</a>,
+and the "webgl" requirement refers to the
+<a href="http://www.khronos.org/webgl/">WebGL API</a>.
+For more information on Chrome 3D graphics support,
+see the help article on
+<a href="http://www.google.com/support/chrome/bin/answer.py?answer=1220892">WebGL and 3D graphics</a>.
+Support for additional requirements checks may be added in the future.
+</p>
+
 
 <h3 id="version">version</h3>
 
diff --git a/chrome/common/extensions/docs/static/whats_new.html b/chrome/common/extensions/docs/static/whats_new.html
index c6bdd0b..890eb56 100644
--- a/chrome/common/extensions/docs/static/whats_new.html
+++ b/chrome/common/extensions/docs/static/whats_new.html
@@ -7,6 +7,7 @@ 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>
@@ -25,6 +26,94 @@ 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
+      <a href="webNavigation.html">web navigation API</a>
+      lets extensions receive notifications about the status
+      of navigation requests.
+      You can use this API to track navigation events.
+    </li>
+    <li> The
+      <a href="permissions.html">optional permissions API</a>
+      lets you control when users are presented with permission requests.
+    </li>
+    <li> The
+      <a href="contentSettings.html">content settings API</a>
+      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">requirements</a> field
+      allows you to declare extension requirements up front.
+      For example, you can use this field
+      to specify that your app requires 3D graphics support
+      in order to use features such as CSS 3D Tranforms or WebGL.
+    </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.
+    </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 limit the supported locales for an
+    <a href="external_extensions.html">external extension</a>
+    by adding the <code>supported_locales</code> attribute
+    to the <code>external_extensions.json</code>.
+    </li>
+  </ul>
+  
+<h4> Changes to existing APIs </h4>
+  <ul>
+    <li>The methods <code>getAllInWindow()</code> and
+    <code>getSelected()</code> have been deprecated.
+    To get details about all tabs in the specified window, use
+    <a href="tabs.html#method-query">chrome.tabs.query()</a>
+    with the argument <code>{'windowId': windowID}</code>.
+    To get the tab that is selected in the specified window, use
+    <code>chrome.tabs.query()</code>
+    with the argument <code>{'active': true}</code>.
+    </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
+    for the
+    <a href="windows.html#type-Window">window "panel"</a> type.
+    By default, the "panel" type creates a popup
+    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
diff --git a/chrome/common/extensions/docs/whats_new.html b/chrome/common/extensions/docs/whats_new.html
index 7230cde..dad3873f 100644
--- a/chrome/common/extensions/docs/whats_new.html
+++ b/chrome/common/extensions/docs/whats_new.html
@@ -336,6 +336,7 @@ 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>
@@ -354,6 +355,94 @@ 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
+      <a href="webNavigation.html">web navigation API</a>
+      lets extensions receive notifications about the status
+      of navigation requests.
+      You can use this API to track navigation events.
+    </li>
+    <li> The
+      <a href="permissions.html">optional permissions API</a>
+      lets you control when users are presented with permission requests.
+    </li>
+    <li> The
+      <a href="contentSettings.html">content settings API</a>
+      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">requirements</a> field
+      allows you to declare extension requirements up front.
+      For example, you can use this field
+      to specify that your app requires 3D graphics support
+      in order to use features such as CSS 3D Tranforms or WebGL.
+    </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.
+    </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 limit the supported locales for an
+    <a href="external_extensions.html">external extension</a>
+    by adding the <code>supported_locales</code> attribute
+    to the <code>external_extensions.json</code>.
+    </li>
+  </ul>
+  
+<h4> Changes to existing APIs </h4>
+  <ul>
+    <li>The methods <code>getAllInWindow()</code> and
+    <code>getSelected()</code> have been deprecated.
+    To get details about all tabs in the specified window, use
+    <a href="tabs.html#method-query">chrome.tabs.query()</a>
+    with the argument <code>{'windowId': windowID}</code>.
+    To get the tab that is selected in the specified window, use
+    <code>chrome.tabs.query()</code>
+    with the argument <code>{'active': true}</code>.
+    </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
+    for the
+    <a href="windows.html#type-Window">window "panel"</a> type.
+    By default, the "panel" type creates a popup
+    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