Remove scheme restriction for extension context menu items.

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

Index: chrome/common/extensions/docs/static/contextMenus.html
diff --git a/chrome/common/extensions/docs/static/contextMenus.html b/chrome/common/extensions/docs/static/contextMenus.html
index 26af21fee830d886b7e224d7bceecf687997371e..7f903c6b423d01458c1712016975d05d2ffe3ce4 100644
--- a/chrome/common/extensions/docs/static/contextMenus.html
+++ b/chrome/common/extensions/docs/static/contextMenus.html
@@ -20,6 +20,9 @@ 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.