Update contentSettings extension API docs.

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

Index: chrome/common/extensions/docs/static/contentSettings.html
diff --git a/chrome/common/extensions/docs/static/contentSettings.html b/chrome/common/extensions/docs/static/contentSettings.html
new file mode 100644
index 0000000000000000000000000000000000000000..7fbeedbd67161f7eca0ef031ce9d404ca7d2b749
--- /dev/null
+++ b/chrome/common/extensions/docs/static/contentSettings.html
@@ -0,0 +1,51 @@
+<div id="pageData-name" class="pageData">Content Settings</div>
+
+<!-- BEGIN AUTHORED CONTENT -->
+<p>
+The content settings module allows you

[Use mkwst_at_chromium.org plz., 2011/10/20 12:17:31]

Weird linebreaks here.

[Bernhard Bauer, 2011/10/21 14:04:18]

Fixed.

+to change settings that control whether websites can use features such as
+cookies, Javascript, and plug-ins.

[battre, 2011/10/20 22:32:12]

Explain here why it is called "content settings".

+</p>
+
+<h2 id="patterns">Content Setting Patterns</h2>

[kathyw, 2011/12/13 02:47:31]

Content Setting Patterns -> Content setting patterns

(we use Title Case only in page names; headings use Sentence case)

+<p>
+You can set patterns that match multiple origins, like <code>youtube.com</code>

[Use mkwst_at_chromium.org plz., 2011/10/20 12:17:31]

How about "Patterns can match multiple origins..."?

It might also be worthwhile to introduce the concept more generally, maybe:
"Content settings are applied to specific websites via <a href='...'>match
patterns</a> that define a setting's scope. `http://*.youtube.com/` matches
youtube.com and all it's subdomains, for example. For further details, see <a
href='...'>the pattern documentation</a>." Kathy, what do you think?

[Bernhard Bauer, 2011/10/21 14:04:18]

Done.

[kathyw, 2011/12/13 02:47:31]

I agree with your comment, Mike. I'd tweak it a bit. Maybe:

You use <em>match patterns</em>
to specify the websites in each content setting's scope.
For example, the match pattern 'http://*.youtube.com/'
specifies youtube.com and all of its subdomains.
For details, see
_Match Patterns_.

+and all subdomains. For details on the format of a pattern, see
+<a href="match_patterns.html">Match Patterns</a>.</p>
+<p>
+Note that there is a restriction on the pattern syntax: For <code>http</code>,

[Use mkwst_at_chromium.org plz., 2011/10/20 12:17:31]

"on the pattern syntax for Content Settings."

[Bernhard Bauer, 2011/10/21 14:04:18]

Done.

+<code>https</code> and <code>ftp</code> URLs the path has to be a wildcard

[battre, 2011/10/20 22:32:12]

URLs *comma*

[Bernhard Bauer, 2011/10/21 14:04:18]

Done.

+(<code>/*</code>). For <code>file</code> URLs, the path has to be completely
+specified and is <strong>not</strong> allowed to contain wildcards.
+</p>
+
+<h3 id="pattern-precedence">Pattern Precedence</h3>

[battre, 2011/10/20 22:32:12]

also explain primary and secondary pattern here?

[Bernhard Bauer, 2011/10/21 14:04:18]

Done.

[kathyw, 2011/12/13 02:47:31]

Pattern Precedence -> Pattern precedence

+<p>
+When more than one content setting rule applies for a given site, the rule with
+the more specific pattern takes precedence.
+</p>
+<p>For example, the pattern <code>http://*.example.com</code> (matching example.com and all subdomains) is more specific than the pattern <code>&lt;all_urls&gt;</code> (matching every URL). Likewise, the pattern <code>http://www.example.com</code> is more specific than <code>http://*.example.com</code>.
+</p>
+
+<h2 id="resourceIdentifiers">Resource Identifiers</h2>

[battre, 2011/10/20 22:32:12]

How do you learn about valid identifiers?

[Bernhard Bauer, 2011/10/21 14:04:18]

Done.

[kathyw, 2011/12/13 02:47:31]

Resource Identifiers -> Resource identifiers

+<p>
+Resource identifiers allow you to specify content settings for specific
+sub-types of a content type. Currently, the only content type that supports

[kathyw, 2011/12/13 02:47:31]

sub-types -> subtypes

+resource identifiers is <code>plugins</code>, where a resource identifier
+identifies a specific plug-in. When applying content settings, first the
+settings for the specific plug-in are checked. If there are no settings found
+for the specific plug-in, the general content settings for plug-ins are checked.

[Use mkwst_at_chromium.org plz., 2011/10/20 12:17:31]

Example?

[Bernhard Bauer, 2011/10/21 14:04:18]

Done.

+</p>
+
+<h2 id="manifest">Manifest</h2>
+<p>You must declare the "contentSettings" permission

[kathyw, 2011/12/13 02:47:31]

Usually the manifest section goes higher up and has a certain format (with
example code). See bookmarks.html for a typical example.

+in your extension's manifest to use the API.</p>

[battre, 2011/10/20 22:32:12]

This section usually goes to the top and contains an example.

[Bernhard Bauer, 2011/10/21 14:04:18]

Done.

+
+<h2 id="examples">Examples</h2>
+
+<p>
+You can find samples of this API on the
+<a href="samples.html#contentSettings">sample page</a>.
+</p>
+
+<!-- END AUTHORED CONTENT -->