App and Extension Documentation: Don't forbid non-standard icon sizes.

chrome/common/extensions/docs/templates/articles/manifest.html

 <h1>Formats: Manifest Files</h1>
 
 
 <p>
 Every extension, installable web app, and theme has a
 <a href="http://www.json.org">JSON</a>-formatted manifest file,
 named <code>manifest.json</code>,
 that provides important information.
 </p>
 
@@ skipping 166 matching lines @@
 Here's an example of specifying the icons:
 </p>
 
 <pre>
 "icons": { "16": "icon16.png",
            "48": "icon48.png",
           "128": "icon128.png" },
 </pre>
 
 <p class="note">
-<b>Important:</b>
-Use only the documented icon sizes.
-<br><br>
-You might notice that Chrome sometimes resizes these icons down to smaller
-sizes. For example, the install dialog might shrink the 128-pixel
-icon down to 69 pixels.
-<br><br>
-However, the details of
-Chrome's UI may change between versions, and these changes assume that
-developers are using the documented sizes. If you use other sizes,
-your icon may look bad in future versions of the browser.
+You may provide icons of any other size you wish, and Chrome will attempt to use
+the best size where appropriate. For example, Windows often requires 32-pixel
+icons, and if the app includes a 32-pixel icon, Chrome will choose that instead
+of shrinking a 48-pixel icon down. However, you should ensure that all of your
+icons are square, or unexpected behavior may result.
 </p>
 
 <p>
 If you upload your extension, app, or theme using the
 <a href="https://chrome.google.com/webstore/developer/dashboard">Chrome Developer Dashboard</a>,
 you'll need to upload additional images,
 including at least one screenshot of your extension.
 For more information,
 see the
 <a href="http://code.google.com/chrome/webstore/">Chrome Web Store
@@ skipping 422 matching lines @@
 goes into more detail about implementing a sandboxing workflow that enables use
 of libraries that would otherwise have issues executing under extension's
 <a href="../extensions/contentSecurityPolicy.html">default Content Security
 Policy</a>.
 </p>
 
 <p>
 Sandboxed page may only be specified when using
 <a href="#manifest_version"><code>manifest_version</code></a> 2 or above.
 </p>