Fix up extension docs to include latest changes to how file URLs work with

Fix up extension docs to include latest changes to how file URLs work with
content scripts.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=51467

[kathyw, 2010-07-01 22:15:39]

Some copyedits.

Do these changes take effect in M6?

http://codereview.chromium.org/2864035/diff/1/3
File chrome/common/extensions/docs/static/match_patterns.html (right):

http://codereview.chromium.org/2864035/diff/1/3#newcode19
chrome/common/extensions/docs/static/match_patterns.html:19: There is also a
special pattern
-> The special pattern

http://codereview.chromium.org/2864035/diff/1/3#newcode20
chrome/common/extensions/docs/static/match_patterns.html:20:
<code>&lt;all_urls&gt;</code>, which will match any URL
, which will match -> matches

http://codereview.chromium.org/2864035/diff/1/3#newcode21
chrome/common/extensions/docs/static/match_patterns.html:21: on the available
schemes.
-> that starts with <code>http</code>, <code>https</code>, <code>file</code>, or
<code>ftp</code>.

(? Is that right? I was guessing. An alternative would be to modify the first
sentence in this paragraph to define "available scheme". E.g. "that begins with
an available scheme (http, https, ...)..."

http://codereview.chromium.org/2864035/diff/1/3#newcode55
chrome/common/extensions/docs/static/match_patterns.html:55: If the
<em>scheme</em> is just <code>*</code>,
delete "just", since there's no other way to use * in the scheme (right?)

http://codereview.chromium.org/2864035/diff/1/3#newcode168
chrome/common/extensions/docs/static/match_patterns.html:168: Matches any URL
withing the mail.google.com host on either the
withing is misspelled, and this is a little unclear. How about:

Matches any URL that starts with http://mail.google.com or
https://mail.google.com.

http://codereview.chromium.org/2864035/diff/1/3#newcode184
chrome/common/extensions/docs/static/match_patterns.html:184: Matches any URL
that uses a permitted scheme (see above for the list of permitted schemes).
we should be consistent about using either "available scheme" or "permitted
scheme". (I rather like "permitted".) Also, "see above" could be a bit more
helpful. Maybe:

...scheme. (See the beginning of this section for the list of permitted
schemes.)

[Matt Perry, 2010-07-02 00:00:45]

Thanks Kathy, it's much better!

http://codereview.chromium.org/2864035/diff/1/3
File chrome/common/extensions/docs/static/match_patterns.html (right):

http://codereview.chromium.org/2864035/diff/1/3#newcode21
chrome/common/extensions/docs/static/match_patterns.html:21: on the available
schemes.
On 2010/07/01 22:15:39, kathyw wrote:
> -> that starts with <code>http</code>, <code>https</code>, <code>file</code>,
or
> <code>ftp</code>.
> 
> (? Is that right? I was guessing. An alternative would be to modify the first
> sentence in this paragraph to define "available scheme". E.g. "that begins
with
> an available scheme (http, https, ...)..."

I went with the second approach, since we might like to change what schemes are
available at some point.

[kathyw, 2010-07-02 00:14:51]

LGTM

Thanks for making those changes!

Now could you remind me... When do these changes take effect? Are they out on
dev channel yet?

[Matt Perry, 2010-07-02 00:25:55]

On 2010/07/02 00:14:51, kathyw wrote:
> LGTM
> 
> Thanks for making those changes!
> 
> Now could you remind me... When do these changes take effect? Are they out on
> dev channel yet?

They were added in this revision:
http://src.chromium.org/viewvc/chrome?view=rev&revision=51295

They missed this week's dev channel release, so they'll be in next week's.