Remove scheme restriction for extension context menu items.

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

 <div id="pageData-name" class="pageData">Context Menus</div>
 
 <!-- BEGIN AUTHORED CONTENT -->
 <p>
 The context menus module allows you
 to add items to Google Chrome's context menu.
 </p>
 
 <p>
 You can choose what types of objects
 your context menu additions apply to,
 such as images, hyperlinks, and pages.
 </P>
 
 <p>
 You can create as many context menu items
 as you need, but if more than one
 from your extension is visible at once,
 Google Chrome automatically collapses them
 into a single parent menu.
 </p>
 
+<p>When we originally released the contextMenus API out of
+experimental, we limited items to only appear on documents (or frames within documents) whose url had a scheme of http/https. We've recently removed that restriction, so your items can appear on any document such as file:// urls, etc. If you'd like to control which pages your items appear on, see the targetUrlPatterns parameter to the create and update methods.</p>

[kathyw, 2011/07/12 22:17:54]

We can tighten this up a bit, plus add line breaks on phrases, as in the rest of
the file. How about (fix to match the facts as needed :):

===========
<p>
Context menu items can appear in any document
(or frame within a document),
even those with file:// or chrome:// URLs.
To control which documents your items can appear in,
specify the targetUrlPatterns field
when you call the create() or update() method.
</p>

<p class="note">
<strong>Version note:</strong>
Before Chrome 14, {PENDING: fix version #?}
only http:// and https:// were allowed.
</p>
===========

NOTE:

* Should targetUrlPatterns be documentUrlPatterns? Or maybe both apply? I'm not
clear on how the context and those two fields interact.

* The document uses "apply to" to refer to the context. I didn't use "apply to"
in the description because I didn't think we were referring only to the
page/frame context.

[asargent_no_longer_on_chrome, 2011/07/14 17:33:30]

 > * Should targetUrlPatterns be documentUrlPatterns? Or maybe both apply? I'm
not
Using documentUrlPatterns is correct, because that controls if an item appears
based on the URL of the top-level document (or frame URL, if the click was in a
frame). 

The targetUrlPatterns is for scoping based on the src/href tag when you right
click on elements like <img>, <a>, etc.

+
 <h2 id="manifest">Manifest</h2>
 <p>You must declare the "contextMenus" permission
 in your extension's manifest to use the API.
 Also, you should specify a 16x16-pixel icon
 for display next to your menu item.
 For example:
 </p>
 
 <pre>{
   "name": "My extension",
   ...
   "permissions": [
     <b>"contextMenus"</b>
   ],
   "icons": {
     <b>"16": "icon-bitty.png",</b>
     "48": "icon-small.png",
     "128": "icon-large.png"
   },
   ...
 }</pre>
 
 <h2 id="examples">Examples</h2>
 
 <p>
 You can find samples of this API on the
 <a href="samples.html#contextMenus">sample page</a>.
 
 <!-- END AUTHORED CONTENT -->