Extension Docs: Remove out dated version notes.

TBR=mkearney@chromium.org

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

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

chrome/common/extensions/docs/apps/contextMenus.html

@@ -240,12 +240,6 @@ To control which documents your items can appear in,
 specify the documentUrlPatterns field
 when you call the create() or update() method.
 </p>
-<p class="note">
-<strong>Version note:</strong>
-Before Chrome 14, <!-- PENDING(asargent): fix version # -->
-your items could appear only in documents with http://
-or https:// URLs.
-</p>
 <h2 id="manifest">Manifest</h2>
 <p>You must declare the "contextMenus" permission
 in your extension's manifest to use the API.

chrome/common/extensions/docs/apps/permissions.html

@@ -314,10 +314,6 @@ You can specify any of the following as optional permissions:
   <li>webRequestBlocking</li>
 </ul>
 <p></p>
-<p class="note">
-  <b>Version note:</b> This list is correct as of Chrome 17.
-  More optional permissions might be allowed in future releases.
-</p>
 <h3 id="request"> Step 3: Request optional permissions </h3>
 <p>
   Request the permissions from within a user gesture using

chrome/common/extensions/docs/extensions/contextMenus.html

@@ -271,12 +271,6 @@ To control which documents your items can appear in,
 specify the documentUrlPatterns field
 when you call the create() or update() method.
 </p>
-<p class="note">
-<strong>Version note:</strong>
-Before Chrome 14, <!-- PENDING(asargent): fix version # -->
-your items could appear only in documents with http://
-or https:// URLs.
-</p>
 <h2 id="manifest">Manifest</h2>
 <p>You must declare the "contextMenus" permission
 in your extension's manifest to use the API.

chrome/common/extensions/docs/extensions/permissions.html

@@ -345,10 +345,6 @@ You can specify any of the following as optional permissions:
   <li>webRequestBlocking</li>
 </ul>
 <p></p>
-<p class="note">
-  <b>Version note:</b> This list is correct as of Chrome 17.
-  More optional permissions might be allowed in future releases.
-</p>
 <h3 id="request"> Step 3: Request optional permissions </h3>
 <p>
   Request the permissions from within a user gesture using

chrome/common/extensions/docs/extensions/xhr.html

@@ -205,16 +205,6 @@ but they're limited by the
 Extensions aren't so limited.
 An extension can talk to remote servers outside of its origin,
 as long as it first requests cross-origin permissions.</p>
-<p class="note">
-<b>Version note:</b>
-As of Chrome 13,
-content scripts can make cross-origin requests
-to the same servers as the rest of the extension.
-Before Chrome 13, a content script couldn't directly make requests;
-instead, it had to
-send a message to its parent extension
-asking the extension to make a cross-origin request.
-</p>
 <h2 id="extension-origin">Extension origin</h2>
 <p>Each running extension exists within its own separate security origin. Without
 requesting additional privileges, the extension can use

chrome/common/extensions/docs/server2/templates/articles/xhr.html

@@ -11,17 +11,6 @@ Extensions aren't so limited.
 An extension can talk to remote servers outside of its origin,
 as long as it first requests cross-origin permissions.</p>
 
-<p class="note">
-<b>Version note:</b>
-As of Chrome 13,
-content scripts can make cross-origin requests
-to the same servers as the rest of the extension.
-Before Chrome 13, a content script couldn't directly make requests;
-instead, it had to
-send a message to its parent extension
-asking the extension to make a cross-origin request.
-</p>
-
 <h2 id="extension-origin">Extension origin</h2>
 <p>Each running extension exists within its own separate security origin. Without
 requesting additional privileges, the extension can use

chrome/common/extensions/docs/server2/templates/intros/contextMenus.html

@@ -26,13 +26,6 @@ specify the documentUrlPatterns field
 when you call the create() or update() method.
 </p>
 
-<p class="note">
-<strong>Version note:</strong>
-Before Chrome 14, 
-your items could appear only in documents with http://
-or https:// URLs.
-</p>
-
 <h2 id="manifest">Manifest</h2>
 <p>You must declare the "contextMenus" permission
 in your extension's manifest to use the API.

chrome/common/extensions/docs/server2/templates/intros/permissions.html

@@ -95,11 +95,6 @@ You can specify any of the following as optional permissions:
 </ul>
 </p>
 
-<p class="note">
-  <b>Version note:</b> This list is correct as of Chrome 17.
-  More optional permissions might be allowed in future releases.
-</p>
-
 <h3 id="request"> Step 3: Request optional permissions </h3>
 <p>
   Request the permissions from within a user gesture using

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

@@ -29,13 +29,6 @@ specify the documentUrlPatterns field
 when you call the create() or update() method.
 </p>
 
-<p class="note">
-<strong>Version note:</strong>
-Before Chrome 14, <!-- PENDING(asargent): fix version # -->
-your items could appear only in documents with http://
-or https:// URLs.
-</p>
-
 <h2 id="manifest">Manifest</h2>
 <p>You must declare the "contextMenus" permission
 in your extension's manifest to use the API.

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

@@ -98,11 +98,6 @@ You can specify any of the following as optional permissions:
 </ul>
 </p>
 
-<p class="note">
-  <b>Version note:</b> This list is correct as of Chrome 17.
-  More optional permissions might be allowed in future releases.
-</p>
-
 <h3 id="request"> Step 3: Request optional permissions </h3>
 <p>
   Request the permissions from within a user gesture using

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

@@ -11,17 +11,6 @@ Extensions aren't so limited.
 An extension can talk to remote servers outside of its origin,
 as long as it first requests cross-origin permissions.</p>
 
-<p class="note">
-<b>Version note:</b>
-As of Chrome 13,
-content scripts can make cross-origin requests
-to the same servers as the rest of the extension.
-Before Chrome 13, a content script couldn't directly make requests;
-instead, it had to
-send a message to its parent extension
-asking the extension to make a cross-origin request.
-</p>
-
 <h2 id="extension-origin">Extension origin</h2>
 <p>Each running extension exists within its own separate security origin. Without
 requesting additional privileges, the extension can use