Extension docs: Update whats_new.html for M21.

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

Index: chrome/common/extensions/docs/static/whats_new.html
diff --git a/chrome/common/extensions/docs/static/whats_new.html b/chrome/common/extensions/docs/static/whats_new.html
index d58a7333070d27adae6861821deb28168d2a61a1..5f24da535154b66b23ee29177785b21ec17370b7 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="#21">Google Chrome 21</a> </li>
   <li> <a href="#20">Google Chrome 20</a> </li>
   <li> <a href="#19">Google Chrome 19</a> </li>
   <li> <a href="#18">Google Chrome 18</a> </li>
@@ -24,18 +25,54 @@ made in recent releases.
   <li> <a href="#6">Google Chrome 6</a> </li>
 </ul>
 
-<p class="note">
-  <strong>New version of packaged apps:</strong><br>
-  There's a new version of
-  <a href="http://developer.chrome.com/trunk/apps/about_apps.html">packaged apps</a>
-  in the <a href="http://dev.chromium.org/getting-involved/dev-channel?">dev channel</a>.
-</p>
-
-<p>
-In addition to the changes listed below,
-check out the
-<a href="experimental.html">experimental APIs</a>.
-</p>
+<h2 id="21"> Google Chrome 21 </h2>
+
+<h4> New Features </h4>
+  <ul>
+    <li>The <a href="manifest.html#sandbox">sandbox manifest entry</a> allows
+      you to define some pages within your extension that are automatically run
+      in a low-privilege sandbox. This sandbox is not bound by the
+      <a href="manifest.html#content_security_policy"
+      >content_security_policy</a>.

[mkearney, 2012/08/13 23:51:50]

Should this be under a "Manifest changes" heading? Also, are we removing apps
information from extension release notes? I'd suggest specifically mentioning
apps in the release note-- 'allows you to define some pages within your apps and
extensions that are automatically...'

[Aaron Boodman, 2012/08/14 00:20:38]

I decided that separating "manifest" changes from "api" changes was not useful.
They are all just features.
Apps has their own release notes mechanism. This one is only published as part
of extensions.

+
+    <li>The <a href="input.ime.html">IME</a> API allows extensions to implement
+      <a href="http://en.wikipedia.org/wiki/Input_method">input method
+      editors</a> on Chrome OS.

[mkearney, 2012/08/13 23:51:50]

There's already an entry for the IME API in Google Chrome 18 which should
probably be removed. Adding a second comment for this.

[Aaron Boodman, 2012/08/14 00:20:38]

That's weird! Removed.

+  </ul>

[mkearney, 2012/08/13 23:51:50]

In addition to the sandbox field, should we also include under "Manifest
changes" something on registering web intents as content type viewers?
Or maybe this belongs in 'Additions to existing features'?

Something like:
<li><a href="manifest.html#intents">Web intents</a>
      can be registered as content type viewers.</li>

[Aaron Boodman, 2012/08/14 00:20:38]

Done.

+
+<h4> Additions to Existing Features </h4>
+  <ul>
+    <li>The events in the <a href="webNavigation.html">Web Navigation API</a>
+      now accept <a href="events.html#declarative">filters</a> which limit the
+      URLs they fire on.
+    <li>The <code><a href="types.html#method-types.ChromeSetting-set"
+      >ChromeSetting.set</a></code> method now has a

[mkearney, 2012/08/13 23:51:50]

Little nit - ChromeSetting.set().

[Aaron Boodman, 2012/08/14 00:20:38]

Done.

+      <code>regular_only</code> scope.
+    <li>The <a href="browsingData.html#type-browsingData.RemovalOptions"
+      >browsingData.RemovalOptions</a> now has an <code>originTypes</code>
+      property.
+    <li>The <code><a href="management.html#method-uninstall"
+      >management.uninstall()</a></code> method now has a <code
+      >showConfirmDialog</code> parameter.

[mkearney, 2012/08/13 23:51:50]

A general comment: we don't need <code> tag for methods within an href.

[Aaron Boodman, 2012/08/14 00:20:38]

Done.

+    <li>The <code><a href="contextMenus.html#method-create"
+      >contextMenus.create()</a></code> method now allows you to specify unique
+      IDs for each item. This is intended to be used with the new
+      <code><a href="contextMenus.html#event-onClicked"
+      >contextMenus.onClicked</a></code> event, to distinguish the clicked item.
+    <li>The <code><a href="browserAction.html#method-setIcon"
+      >browserAction.setIcon()</a></code> and
+      <code><a href="pageAction.html#method-setIcon"
+      >pageAction.setIcon()</a></code> methods now accept optional callbacks.
+    <li>The <code><a href="privacy.html#property-websites"
+      >privacy.website</a></code> namespace now has a <code
+      >protectedContentEnabled</code> property.
+    <li>The <code>index</code> parameter to the <a href="tabs.html#method-move"
+      >tabs.move()</a></code> method now accepts <code>-1</code> to indicate
+      that the tab should be placed at the end.

[mkearney, 2012/08/13 23:51:50]

Should we also mention that the "index" parameter is now optional for
chrome.tabs.move?

http://chromiumcodereview.appspot.com/9699065/

+    <li>The <code>windowId</code> parameter to the
+      <code><a href="tabs.html#method-highlight">tabs.highlight()</a></code>
+      method is now optional.
+  </ul>
 
 <h2 id="20"> Google Chrome 20 </h2>