Merge 127979 - This includes the extension release notes for Chrome 18.

Here's a link to the staged docs:

http://www.corp.google.com/~mkearney/no_crawl/chromium/staging/whats_new.html

Review URL: https://chromiumcodereview.appspot.com/9705111

TBR=mihaip@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9791071

git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@129427 0039d316-1c4b-4281-b951-d872f2087c98

2 files changed, 165 insertions, 273 deletions

diff --git a/chrome/common/extensions/docs/static/whats_new.html b/chrome/common/extensions/docs/static/whats_new.html
index 890eb56..ec60568 100644
--- a/chrome/common/extensions/docs/static/whats_new.html
+++ b/chrome/common/extensions/docs/static/whats_new.html
@@ -30,58 +30,49 @@ check out the
 
 <h4> New APIs </h4>
   <ul>
-    <li> The
+    <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
+    <li>The
       <a href="permissions.html">optional permissions API</a>
       lets you control when users are presented with permission requests.
-    </li>
-    <li> The
+    <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
+    <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
+    <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
+    <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>
@@ -94,24 +85,19 @@ check out the
     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
+    <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
+    the <code>tabID</code> defaults
+    to the selected tab of the current window.
+    <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
+    <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>
@@ -123,50 +109,41 @@ installation</a> feature, which lets your website help users install extensions
 
 <h4> Manifest changes </h4>
   <ul>
-    <li> The new
+    <li>The new
       <a href="manifest.html#offline_enabled">offline_enabled</a> field
       lets you specify that your app works well even without an internet
       connection.
-    </li>
   </ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
-    <li>
-      You can retrieve permission warnings using the new management API methods
+    <li>You can retrieve permission warnings using the new management API methods
       <a href="management.html#method-getPermissionWarningsById">getPermissionWarningsById()</a>
       and
       <a href="management.html#method-getPermissionWarningsByManifest">getPermissionWarningsByManifest()</a>.
-    </li>
-    <li>
-      The management API’s
+    <li>The management API’s
       <a href="management.html#type-ExtensionInfo">ExtensionInfo</a> object has
       a new field, <code>offlineEnabled</code>.
-    </li>
-    <li>
-      You can now <a href="i18n.html">internationalize</a> content script CSS
+    <li>You can now <a href="i18n.html">internationalize</a> content script CSS
       files by using <code>__MSG_messagename__</code> placeholders.
-    </li>
   </ul>
 
 <h4> Changes to existing APIs </h4>
   <ul>
-    <li>
-      The callback for the <a href="tabs.html#method-update">tabs.update</a>
+    <li>The callback for the <a href="tabs.html#method-update">tabs.update</a>
       method is passed <code>null</code> instead of the tab details if the
       extension does not have the "tabs" permission.
-    </li>
   </ul>
 
 <h2 id="14"> Google Chrome 14 </h2>
 
 <h4> New APIs </h4>
   <ul>
-    <li> The <a href="tts.html">tts API</a>
-      lets extensions generate speech from text. </li>
-    <li> The <a href="ttsEngine.html">ttsEngine API</a>
-      lets extensions implement text-to-speech (TTS) engines. </li>
-    <li> Extensions that are distributed through the Chrome Web Store
+    <li>The <a href="tts.html">tts API</a>
+      lets extensions generate speech from text.
+    <li>The <a href="ttsEngine.html">ttsEngine API</a>
+      lets extensions implement text-to-speech (TTS) engines.
+    <li>Extensions that are distributed through the Chrome Web Store
       can now include Native Client modules.
       No special manifest entry is necessary, as you can see from the
       <a href="http://code.google.com/p/naclports/source/browse#svn%2Ftrunk%2Fsrc%2Fpackages%2Flibraries%2Fnethack-3.4.3">NetHack example</a>.
@@ -177,90 +154,74 @@ installation</a> feature, which lets your website help users install extensions
 
 <h4> Manifest changes </h4>
   <ul>
-    <li> The new
+    <li>The new
       <a href="manifest.html#content_security_policy">content_security_policy</a> field
       can help prevent
       <a href="http://blog.chromium.org/2011/07/writing-extensions-more-securely.html">cross-site scripting vulnerabilities</a>
       in your extension.
-    </li>
-    <li> The new <a href="manifest.html#nacl_modules">nacl_modules</a> field
+    <li>The new <a href="manifest.html#nacl_modules">nacl_modules</a> field
       lets you register Native Client modules
       as content handlers for MIME types.
-      </li>
   </ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
-    <li>
-      <a href="contextMenus.html">Context menu</a> items
+    <li><a href="contextMenus.html">Context menu</a> items
       can now appear even in documents
       that have file:// or chrome:// URLs.
       Previously, they were restricted to documents with
       http:// or https:// URLs.
-    </li>
-    <li>
-      An optional <code>drawAttention</code> field in
+    <li>An optional <code>drawAttention</code> field in
       <a href="windows.html#method-update">chrome.windows.update()</a>'s
       <code>updateInfo</code> object lets you specify that the window
       should entice the user to change focus to it.
-    </li>
-    <li>
-      The new
+    <li>The new
       <a href="bookmarks.html#method-getSubTree">bookmarks.getSubTree()</a>
       function lets you retrieve just part of the Bookmarks hierarchy.
-    </li>
   </ul>
 
 <h4> Changes to existing APIs </h4>
   <ul>
-    <li>
-      The "tabs" permission is no longer required for
+    <li>The "tabs" permission is no longer required for
       <a href="tabs.html#method-remove">tabs.remove</a> and
       <a href="tabs.html#event-onRemoved">tabs.onRemoved</a>.
-    </li>
   </ul>
 
 <h2 id="13"> Google Chrome 13 </h2>
 
 <h4> New APIs </h4>
   <ul>
-    <li> The <a href="proxy.html">proxy API</a>
+    <li>The <a href="proxy.html">proxy API</a>
       lets extensions manage Chrome's proxy settings.
-      </li>
-    <li> The
+    <li>The
       <a href="types.html#type-ChromeSetting">chrome.types.ChromeSetting</a> prototype
       provides an interface to browser settings;
       it's used by the proxy API.
-      </li>
     <li> <em>Chrome OS only:</em>
       The <a href="fileBrowserHandler.html">fileBrowserHandler API</a>
       lets you extend the Chrome OS file browser.
-      </li>
   </ul>
 
 <h4> Manifest changes </h4>
   <ul>
-    <li> A new <code>exclude_matches</code> item
+    <li>A new <code>exclude_matches</code> item
       in the "content_scripts" field
       lets you target your content script more precisely.
       For details, see
       <a href="content_scripts.html#match-patterns-globs">Match patterns and globs</a>.
-      </li>
-    <li> New "clipboardRead" and "clipboardWrite"
+    <li>New "clipboardRead" and "clipboardWrite"
       <a href="manifest.html#permissions">permissions</a>
       specify capabilities for <code>document.execCommand()</code>.
-      </li>
   </ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
-    <li> Content scripts can now make
+    <li>Content scripts can now make
       <a href="xhr.html">cross-origin XMLHttpRequests</a>
       to the same sites that their parent extension can,
       eliminating the need to relay these requests
       through a background page.
-      </li>
-    <li> You can now use <code>@run-at</code>
+    <li>You can now use <code>@run-at</code>
       in an imported Greasemonkey script
       to control when the script is injected.
       It works the same way as
@@ -272,29 +233,26 @@ installation</a> feature, which lets your website help users install extensions
 
 <h4> Additions to existing APIs </h4>
   <ul>
-    <li> Two new <code>chrome.extension</code>
+    <li>Two new <code>chrome.extension</code>
       methods&mdash;<a href="extension.html#method-isAllowedFileSchemeAccess">isAllowedFileSchemeAccess()</a> and
       <a href="extension.html#method-isAllowedIncognitoAccess">isAllowedIncognitoAccess()</a>&mdash;let you
       determine whether your extension has increased access,
       which the user specifies using the extensions management page
       (<b>chrome://extensions</b>).
-      </li>
-    <li> The <a href="windows.html#method-create">chrome.windows.create()</a>
+    <li>The <a href="windows.html#method-create">chrome.windows.create()</a>
       method can now take a <code>focused</code> value.
       Previously, all new windows had the keyboard focus;
       now you can create windows without interrupting the user's typing.
-      </li>
-    <li> If the manifest specifies "experimental" permission,
+    <li>If the manifest specifies "experimental" permission,
       your extension can specify "panel" as the value of
       the <code>type</code> field in
       the <a href="windows.html#method-create">chrome.windows.create()</a>
       method
       or the <a href="windows.html#type-Window">Window</a> type.
-      </li>
-    <li> The <a href="cookies.html#event-onChanged">onChanged</a>
+    <li>The <a href="cookies.html#event-onChanged">onChanged</a>
       event of <code>chrome.cookies</code>
-      now has a <code>cause</code> parameter. </li>
-    <li> The <code>chrome.contextMenus</code>
+      now has a <code>cause</code> parameter.
+    <li>The <code>chrome.contextMenus</code>
       <a href="contextMenus.html#method-create">create()</a> and
       <a href="contextMenus.html#method-update">update()</a>
       methods now let you specify a context value of "frame".
@@ -304,8 +262,7 @@ installation</a> feature, which lets your website help users install extensions
 
 <h4> Changes to existing APIs </h4>
   <ul>
-    <li>
-      For security reasons, you can no longer call
+    <li>For security reasons, you can no longer call
       <a href="tabs.html#method-captureVisibleTab">chrome.tab.captureVisibleTab()</a>
       on just any tab.
       Instead, you now must have
@@ -313,27 +270,22 @@ installation</a> feature, which lets your website help users install extensions
       for the URL displayed by that tab.
       To get the previous behavior,
       specify <code>&lt;all_urls></code> for the host permission.
-    </li>
   </ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
-    <li>
-      The management API's
+    <li>The management API's
       <a href="management.html#type-ExtensionInfo">ExtensionInfo</a> object
       now has a <code>homepageUrl</code> property.
-    </li>
-    <li> The management API now lets you get the icons of
+    <li>The management API now lets you get the icons of
       disabled apps and extensions.
       Also, you can now modify the regular icon's URL
       to get its disabled equivalent.
       See <a href="management.html#type-IconInfo">IconInfo</a> for details.
-    </li>
-    <li> The cookies API
+    <li>The cookies API
       <a href="cookies.html#method-set">set()</a>
       and <a href="cookies.html#method-remove">remove()</a> methods
       can now take callbacks.
-    </li>
   </ul>
 
 <h2 id="10"> Google Chrome 10 </h2>
@@ -344,19 +296,17 @@ installation</a> feature, which lets your website help users install extensions
       extends the life of Chrome,
       allowing your extension or app
       to run even when Chrome has no windows open.
-      </li>
   </ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
-    <li> The <a href="windows.html#method-create">chrome.windows.create()</a>
+    <li>The <a href="windows.html#method-create">chrome.windows.create()</a>
       method now has a <code>tabId</code> field.
       You can use it to move a tab or panel into a new window.
       <p class="note">
       <b>Note:</b>
       This change was incorrectly attributed to Chrome 9
       in previous release notes.
-    </li>
   </ul>
 
 <h2 id="9"> Google Chrome 9 </h2>
@@ -364,29 +314,29 @@ installation</a> feature, which lets your website help users install extensions
 <h4> New APIs </h4>
   <ul>
     <li>The <a href="omnibox.html">omnibox API</a> allows you to
-      register a keyword with Chrome's address bar. </li>
+      register a keyword with Chrome's address bar.
   </ul>
 
 <h4> Manifest changes </h4>
   <ul>
-    <li> The <a href="manifest.html#homepage_url">homepage_url</a> field
-      lets you specify the extension or app's homepage. </li>
+    <li>The <a href="manifest.html#homepage_url">homepage_url</a> field
+      lets you specify the extension or app's homepage.
   </ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
-    <li> The <a href="tabs.html#type-Tab">Tab</a> object
+    <li>The <a href="tabs.html#type-Tab">Tab</a> object
       now has a <code>pinned</code> property
       that's reflected in various <code>chrome.tabs</code> methods.
       For example,
       you can <a href="tabs.html#method-create">create</a>
-      a pinned tab. </li>
-    <li> The <a href="windows.html#method-create">chrome.windows.create()</a>
+      a pinned tab.
+    <li>The <a href="windows.html#method-create">chrome.windows.create()</a>
       method can now take a list of URLs,
-      letting you create multiple tabs in the new window. </li>
-    <li> The new
+      letting you create multiple tabs in the new window.
+    <li>The new
       <a href="management.html#method-get">chrome.management.get()</a> method
-      lets you get information about the specified extension or app. </li>
+      lets you get information about the specified extension or app.
   </ul>
 
 
@@ -402,26 +352,22 @@ No API or manifest changes worth noting.
 
 <h4> New APIs </h4>
   <ul>
-    <li> All users can now install
+    <li>All users can now install
       <a href="http://code.google.com/chrome/apps/index.html">apps</a>;
       packaged apps can use extension APIs.
-      </li>
-    <li> The <a href="management.html">management API</a>
+    <li>The <a href="management.html">management API</a>
       lets you work with installed apps and extensions.
-      </li>
   </ul>
 
 <h4> Manifest changes </h4>
   <ul>
-    <li> Introduced <a href="manifest.html#incognito">split incognito</a>
+    <li>Introduced <a href="manifest.html#incognito">split incognito</a>
       mode as the default for installable web apps
       (also available to extensions).
-      </li>
-    <li> The <a href="tabs.html">tabs API</a>
+    <li>The <a href="tabs.html">tabs API</a>
       <code>create()</code> and <code>update()</code> methods
       no longer require the "tabs" permission, removing one common cause of
       <a href="permission_warnings.html">scary dialogs</a>.
-      </li>
   </ul>
 
 
@@ -430,34 +376,34 @@ No API or manifest changes worth noting.
 <h4> New APIs </h4>
   <ul>
     <li>The <a href="contextMenus.html">context menus API</a> allows you to
-      add context menus to pages or specific objects on a page. </li>
+      add context menus to pages or specific objects on a page.
     <li>The <a href="cookies.html">cookies API</a> allows you to manage the
-      browser's cookie system.  </li>
+      browser's cookie system.
     <li>The <a href="idle.html">idle API</a> allows you to detect when the
-      machine's idle state changes. </li>
+      machine's idle state changes.
   </ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
     <li>The <a
       href="extension.html#method-getViews">chrome.extension.getViews()</a>
-      method can now return popup views. </li>
+      method can now return popup views.
     <li>A new <a
       href="windows.html#property-WINDOW_ID_NONE">WINDOW_ID_NONE</a> constant
-      identifies when focus shifts away from the browser. </li>
+      identifies when focus shifts away from the browser.
     <li>The new <a
       href="tabs.html#method-getCurrent">chrome.tabs.getCurrent()</a> method
-      returns the tab associated with the currently executing script. </li>
+      returns the tab associated with the currently executing script.
   </ul>
 
 <h4> Manifest changes </h4>
   <ul>
     <li>The <a href="manifest.html#geolocation">geolocation</a> permission
-      gives an extension access to the user's physical location. </li>
+      gives an extension access to the user's physical location.
     <li><a href="match_patterns.html">Match patterns</a> can now select all
-      schemes or all URLs. </li>
+      schemes or all URLs.
     <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>
+      management page.
   </ul>
 
diff --git a/chrome/common/extensions/docs/whats_new.html b/chrome/common/extensions/docs/whats_new.html
index 05a79f1..eb33b98 100644
--- a/chrome/common/extensions/docs/whats_new.html
+++ b/chrome/common/extensions/docs/whats_new.html
@@ -376,59 +376,50 @@ check out the
 
 <h4> New APIs </h4>
   <ul>
-    <li> The
+    <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
+    </li><li>The
       <a href="permissions.html">optional permissions API</a>
       lets you control when users are presented with permission requests.
-    </li>
-    <li> The
+    </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>
+  </li></ul>
 
 <h4> Manifest changes </h4>
   <ul>
-    <li> The new
+    <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>
+  </li></ul>
   
 <h4> Additions to existing APIs </h4>
   <ul>
-    <li> The new
+    <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
+    </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
+    </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
+    </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>
+  </li></ul>
   
 <h4> Changes to existing APIs </h4>
   <ul>
@@ -440,25 +431,20 @@ check out the
     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
+    </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
+    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
+    </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>
+  </li></ul>
 
 <h2 id="15"> Google Chrome 15 </h2>
 
@@ -469,50 +455,41 @@ installation</a> feature, which lets your website help users install extensions
 
 <h4> Manifest changes </h4>
   <ul>
-    <li> The new
+    <li>The new
       <a href="manifest.html#offline_enabled">offline_enabled</a> field
       lets you specify that your app works well even without an internet
       connection.
-    </li>
-  </ul>
+  </li></ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
-    <li>
-      You can retrieve permission warnings using the new management API methods
+    <li>You can retrieve permission warnings using the new management API methods
       <a href="management.html#method-getPermissionWarningsById">getPermissionWarningsById()</a>
       and
       <a href="management.html#method-getPermissionWarningsByManifest">getPermissionWarningsByManifest()</a>.
-    </li>
-    <li>
-      The management API’s
+    </li><li>The management API’s
       <a href="management.html#type-ExtensionInfo">ExtensionInfo</a> object has
       a new field, <code>offlineEnabled</code>.
-    </li>
-    <li>
-      You can now <a href="i18n.html">internationalize</a> content script CSS
+    </li><li>You can now <a href="i18n.html">internationalize</a> content script CSS
       files by using <code>__MSG_messagename__</code> placeholders.
-    </li>
-  </ul>
+  </li></ul>
 
 <h4> Changes to existing APIs </h4>
   <ul>
-    <li>
-      The callback for the <a href="tabs.html#method-update">tabs.update</a>
+    <li>The callback for the <a href="tabs.html#method-update">tabs.update</a>
       method is passed <code>null</code> instead of the tab details if the
       extension does not have the "tabs" permission.
-    </li>
-  </ul>
+  </li></ul>
 
 <h2 id="14"> Google Chrome 14 </h2>
 
 <h4> New APIs </h4>
   <ul>
-    <li> The <a href="tts.html">tts API</a>
-      lets extensions generate speech from text. </li>
-    <li> The <a href="ttsEngine.html">ttsEngine API</a>
-      lets extensions implement text-to-speech (TTS) engines. </li>
-    <li> Extensions that are distributed through the Chrome Web Store
+    <li>The <a href="tts.html">tts API</a>
+      lets extensions generate speech from text.
+    </li><li>The <a href="ttsEngine.html">ttsEngine API</a>
+      lets extensions implement text-to-speech (TTS) engines.
+    </li><li>Extensions that are distributed through the Chrome Web Store
       can now include Native Client modules.
       No special manifest entry is necessary, as you can see from the
       <a href="http://code.google.com/p/naclports/source/browse#svn%2Ftrunk%2Fsrc%2Fpackages%2Flibraries%2Fnethack-3.4.3">NetHack example</a>.
@@ -523,90 +500,74 @@ installation</a> feature, which lets your website help users install extensions
 
 <h4> Manifest changes </h4>
   <ul>
-    <li> The new
+    <li>The new
       <a href="manifest.html#content_security_policy">content_security_policy</a> field
       can help prevent
       <a href="http://blog.chromium.org/2011/07/writing-extensions-more-securely.html">cross-site scripting vulnerabilities</a>
       in your extension.
-    </li>
-    <li> The new <a href="manifest.html#nacl_modules">nacl_modules</a> field
+    </li><li>The new <a href="manifest.html#nacl_modules">nacl_modules</a> field
       lets you register Native Client modules
       as content handlers for MIME types.
-      </li>
-  </ul>
+  </li></ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
-    <li>
-      <a href="contextMenus.html">Context menu</a> items
+    <li><a href="contextMenus.html">Context menu</a> items
       can now appear even in documents
       that have file:// or chrome:// URLs.
       Previously, they were restricted to documents with
       http:// or https:// URLs.
-    </li>
-    <li>
-      An optional <code>drawAttention</code> field in
+    </li><li>An optional <code>drawAttention</code> field in
       <a href="windows.html#method-update">chrome.windows.update()</a>'s
       <code>updateInfo</code> object lets you specify that the window
       should entice the user to change focus to it.
-    </li>
-    <li>
-      The new
+    </li><li>The new
       <a href="bookmarks.html#method-getSubTree">bookmarks.getSubTree()</a>
       function lets you retrieve just part of the Bookmarks hierarchy.
-    </li>
-  </ul>
+  </li></ul>
 
 <h4> Changes to existing APIs </h4>
   <ul>
-    <li>
-      The "tabs" permission is no longer required for
+    <li>The "tabs" permission is no longer required for
       <a href="tabs.html#method-remove">tabs.remove</a> and
       <a href="tabs.html#event-onRemoved">tabs.onRemoved</a>.
-    </li>
-  </ul>
+  </li></ul>
 
 <h2 id="13"> Google Chrome 13 </h2>
 
 <h4> New APIs </h4>
   <ul>
-    <li> The <a href="proxy.html">proxy API</a>
+    <li>The <a href="proxy.html">proxy API</a>
       lets extensions manage Chrome's proxy settings.
-      </li>
-    <li> The
+    </li><li>The
       <a href="types.html#type-ChromeSetting">chrome.types.ChromeSetting</a> prototype
       provides an interface to browser settings;
       it's used by the proxy API.
-      </li>
-    <li> <em>Chrome OS only:</em>
+    </li><li> <em>Chrome OS only:</em>
       The <a href="fileBrowserHandler.html">fileBrowserHandler API</a>
       lets you extend the Chrome OS file browser.
-      </li>
-  </ul>
+  </li></ul>
 
 <h4> Manifest changes </h4>
   <ul>
-    <li> A new <code>exclude_matches</code> item
+    <li>A new <code>exclude_matches</code> item
       in the "content_scripts" field
       lets you target your content script more precisely.
       For details, see
       <a href="content_scripts.html#match-patterns-globs">Match patterns and globs</a>.
-      </li>
-    <li> New "clipboardRead" and "clipboardWrite"
+    </li><li>New "clipboardRead" and "clipboardWrite"
       <a href="manifest.html#permissions">permissions</a>
       specify capabilities for <code>document.execCommand()</code>.
-      </li>
-  </ul>
+  </li></ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
-    <li> Content scripts can now make
+    <li>Content scripts can now make
       <a href="xhr.html">cross-origin XMLHttpRequests</a>
       to the same sites that their parent extension can,
       eliminating the need to relay these requests
       through a background page.
-      </li>
-    <li> You can now use <code>@run-at</code>
+    </li><li>You can now use <code>@run-at</code>
       in an imported Greasemonkey script
       to control when the script is injected.
       It works the same way as
@@ -618,29 +579,26 @@ installation</a> feature, which lets your website help users install extensions
 
 <h4> Additions to existing APIs </h4>
   <ul>
-    <li> Two new <code>chrome.extension</code>
+    <li>Two new <code>chrome.extension</code>
       methods—<a href="extension.html#method-isAllowedFileSchemeAccess">isAllowedFileSchemeAccess()</a> and
       <a href="extension.html#method-isAllowedIncognitoAccess">isAllowedIncognitoAccess()</a>—let you
       determine whether your extension has increased access,
       which the user specifies using the extensions management page
       (<b>chrome://extensions</b>).
-      </li>
-    <li> The <a href="windows.html#method-create">chrome.windows.create()</a>
+    </li><li>The <a href="windows.html#method-create">chrome.windows.create()</a>
       method can now take a <code>focused</code> value.
       Previously, all new windows had the keyboard focus;
       now you can create windows without interrupting the user's typing.
-      </li>
-    <li> If the manifest specifies "experimental" permission,
+    </li><li>If the manifest specifies "experimental" permission,
       your extension can specify "panel" as the value of
       the <code>type</code> field in
       the <a href="windows.html#method-create">chrome.windows.create()</a>
       method
       or the <a href="windows.html#type-Window">Window</a> type.
-      </li>
-    <li> The <a href="cookies.html#event-onChanged">onChanged</a>
+    </li><li>The <a href="cookies.html#event-onChanged">onChanged</a>
       event of <code>chrome.cookies</code>
-      now has a <code>cause</code> parameter. </li>
-    <li> The <code>chrome.contextMenus</code>
+      now has a <code>cause</code> parameter.
+    </li><li>The <code>chrome.contextMenus</code>
       <a href="contextMenus.html#method-create">create()</a> and
       <a href="contextMenus.html#method-update">update()</a>
       methods now let you specify a context value of "frame".
@@ -650,8 +608,7 @@ installation</a> feature, which lets your website help users install extensions
 
 <h4> Changes to existing APIs </h4>
   <ul>
-    <li>
-      For security reasons, you can no longer call
+    <li>For security reasons, you can no longer call
       <a href="tabs.html#method-captureVisibleTab">chrome.tab.captureVisibleTab()</a>
       on just any tab.
       Instead, you now must have
@@ -659,28 +616,23 @@ installation</a> feature, which lets your website help users install extensions
       for the URL displayed by that tab.
       To get the previous behavior,
       specify <code>&lt;all_urls&gt;</code> for the host permission.
-    </li>
-  </ul>
+  </li></ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
-    <li>
-      The management API's
+    <li>The management API's
       <a href="management.html#type-ExtensionInfo">ExtensionInfo</a> object
       now has a <code>homepageUrl</code> property.
-    </li>
-    <li> The management API now lets you get the icons of
+    </li><li>The management API now lets you get the icons of
       disabled apps and extensions.
       Also, you can now modify the regular icon's URL
       to get its disabled equivalent.
       See <a href="management.html#type-IconInfo">IconInfo</a> for details.
-    </li>
-    <li> The cookies API
+    </li><li>The cookies API
       <a href="cookies.html#method-set">set()</a>
       and <a href="cookies.html#method-remove">remove()</a> methods
       can now take callbacks.
-    </li>
-  </ul>
+  </li></ul>
 
 <h2 id="10"> Google Chrome 10 </h2>
 
@@ -690,50 +642,48 @@ installation</a> feature, which lets your website help users install extensions
       extends the life of Chrome,
       allowing your extension or app
       to run even when Chrome has no windows open.
-      </li>
-  </ul>
+  </li></ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
-    <li> The <a href="windows.html#method-create">chrome.windows.create()</a>
+    <li>The <a href="windows.html#method-create">chrome.windows.create()</a>
       method now has a <code>tabId</code> field.
       You can use it to move a tab or panel into a new window.
       <p class="note">
       <b>Note:</b>
       This change was incorrectly attributed to Chrome 9
       in previous release notes.
-    </p></li>
-  </ul>
+  </p></li></ul>
 
 <h2 id="9"> Google Chrome 9 </h2>
 
 <h4> New APIs </h4>
   <ul>
     <li>The <a href="omnibox.html">omnibox API</a> allows you to
-      register a keyword with Chrome's address bar. </li>
-  </ul>
+      register a keyword with Chrome's address bar.
+  </li></ul>
 
 <h4> Manifest changes </h4>
   <ul>
-    <li> The <a href="manifest.html#homepage_url">homepage_url</a> field
-      lets you specify the extension or app's homepage. </li>
-  </ul>
+    <li>The <a href="manifest.html#homepage_url">homepage_url</a> field
+      lets you specify the extension or app's homepage.
+  </li></ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
-    <li> The <a href="tabs.html#type-Tab">Tab</a> object
+    <li>The <a href="tabs.html#type-Tab">Tab</a> object
       now has a <code>pinned</code> property
       that's reflected in various <code>chrome.tabs</code> methods.
       For example,
       you can <a href="tabs.html#method-create">create</a>
-      a pinned tab. </li>
-    <li> The <a href="windows.html#method-create">chrome.windows.create()</a>
+      a pinned tab.
+    </li><li>The <a href="windows.html#method-create">chrome.windows.create()</a>
       method can now take a list of URLs,
-      letting you create multiple tabs in the new window. </li>
-    <li> The new
+      letting you create multiple tabs in the new window.
+    </li><li>The new
       <a href="management.html#method-get">chrome.management.get()</a> method
-      lets you get information about the specified extension or app. </li>
-  </ul>
+      lets you get information about the specified extension or app.
+  </li></ul>
 
 
 <h2 id="8"> Google Chrome 8 </h2>
@@ -748,27 +698,23 @@ No API or manifest changes worth noting.
 
 <h4> New APIs </h4>
   <ul>
-    <li> All users can now install
+    <li>All users can now install
       <a href="http://code.google.com/chrome/apps/index.html">apps</a>;
       packaged apps can use extension APIs.
-      </li>
-    <li> The <a href="management.html">management API</a>
+    </li><li>The <a href="management.html">management API</a>
       lets you work with installed apps and extensions.
-      </li>
-  </ul>
+  </li></ul>
 
 <h4> Manifest changes </h4>
   <ul>
-    <li> Introduced <a href="manifest.html#incognito">split incognito</a>
+    <li>Introduced <a href="manifest.html#incognito">split incognito</a>
       mode as the default for installable web apps
       (also available to extensions).
-      </li>
-    <li> The <a href="tabs.html">tabs API</a>
+    </li><li>The <a href="tabs.html">tabs API</a>
       <code>create()</code> and <code>update()</code> methods
       no longer require the "tabs" permission, removing one common cause of
       <a href="permission_warnings.html">scary dialogs</a>.
-      </li>
-  </ul>
+  </li></ul>
 
 
 <h2 id="6">Google Chrome 6</h2>
@@ -776,33 +722,33 @@ No API or manifest changes worth noting.
 <h4> New APIs </h4>
   <ul>
     <li>The <a href="contextMenus.html">context menus API</a> allows you to
-      add context menus to pages or specific objects on a page. </li>
-    <li>The <a href="cookies.html">cookies API</a> allows you to manage the
-      browser's cookie system.  </li>
-    <li>The <a href="idle.html">idle API</a> allows you to detect when the
-      machine's idle state changes. </li>
-  </ul>
+      add context menus to pages or specific objects on a page.
+    </li><li>The <a href="cookies.html">cookies API</a> allows you to manage the
+      browser's cookie system.
+    </li><li>The <a href="idle.html">idle API</a> allows you to detect when the
+      machine's idle state changes.
+  </li></ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
     <li>The <a href="extension.html#method-getViews">chrome.extension.getViews()</a>
-      method can now return popup views. </li>
-    <li>A new <a href="windows.html#property-WINDOW_ID_NONE">WINDOW_ID_NONE</a> constant
-      identifies when focus shifts away from the browser. </li>
-    <li>The new <a href="tabs.html#method-getCurrent">chrome.tabs.getCurrent()</a> method
-      returns the tab associated with the currently executing script. </li>
-  </ul>
+      method can now return popup views.
+    </li><li>A new <a href="windows.html#property-WINDOW_ID_NONE">WINDOW_ID_NONE</a> constant
+      identifies when focus shifts away from the browser.
+    </li><li>The new <a href="tabs.html#method-getCurrent">chrome.tabs.getCurrent()</a> method
+      returns the tab associated with the currently executing script.
+  </li></ul>
 
 <h4> Manifest changes </h4>
   <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"
+      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>
+      management page.
+  </li></ul>
 
 </div>