| OLD | NEW |
| 1 <h2 id="manifest">Manifest</h2> | 1 <h2 id="manifest">Manifest</h2> |
| 2 <p>You must declare the "contentSettings" permission | 2 <p>You must declare the "contentSettings" permission |
| 3 in your extension's manifest to use the API. | 3 in your extension's manifest to use the API. |
| 4 For example:</p> | 4 For example:</p> |
| 5 <pre data-filename="manifest.json"> | 5 <pre data-filename="manifest.json"> |
| 6 { | 6 { |
| 7 "name": "My extension", | 7 "name": "My extension", |
| 8 ... | 8 ... |
| 9 <b>"permissions": [ | 9 <b>"permissions": [ |
| 10 "contentSettings" | 10 "contentSettings" |
| 11 ]</b>, | 11 ]</b>, |
| 12 ... | 12 ... |
| 13 } | 13 } |
| 14 </pre> | 14 </pre> |
| 15 | 15 |
| 16 | 16 |
| 17 <h2 id="patterns">Content setting patterns</h2> | 17 <h2 id="patterns">Content setting patterns</h2> |
| 18 <p> | 18 <p> |
| 19 You can use patterns to specify the websites that each content setting affects. | 19 You can use patterns to specify the websites that each content setting affects. |
| 20 For example, <code>http://*.youtube.com/*</code> specifies youtube.com and all | 20 For example, <code>http://*.youtube.com/*</code> specifies youtube.com and all |
| 21 of its subdomains. The syntax for content setting patterns is the same as for | 21 of its subdomains. The syntax for content setting patterns is the same as for |
| 22 <a href="match_patterns.html">match patterns</a>, with a few differences: | 22 <a href="match_patterns">match patterns</a>, with a few differences: |
| 23 <ul><li>For <code>http</code>, | 23 <ul><li>For <code>http</code>, |
| 24 <code>https</code>, and <code>ftp</code> URLs, the path must be a wildcard | 24 <code>https</code>, and <code>ftp</code> URLs, the path must be a wildcard |
| 25 (<code>/*</code>). For <code>file</code> URLs, the path must be completely | 25 (<code>/*</code>). For <code>file</code> URLs, the path must be completely |
| 26 specified and <strong>must not</strong> contain wildcards.</li> | 26 specified and <strong>must not</strong> contain wildcards.</li> |
| 27 <li>In contrast to match patterns, content setting patterns can specify a port | 27 <li>In contrast to match patterns, content setting patterns can specify a port |
| 28 number. If a port number is specified, the pattern only matches websites with | 28 number. If a port number is specified, the pattern only matches websites with |
| 29 that port. If no port number is specified, the pattern matches all ports. | 29 that port. If no port number is specified, the pattern matches all ports. |
| 30 </li> | 30 </li> |
| 31 </ul> | 31 </ul> |
| 32 </p> | 32 </p> |
| (...skipping 97 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 130 You can get a list of resource identifiers for a content type by calling the | 130 You can get a list of resource identifiers for a content type by calling the |
| 131 $(ref:contentSettings.ContentSetting.getResourceIdentifiers) method. The returne
d list | 131 $(ref:contentSettings.ContentSetting.getResourceIdentifiers) method. The returne
d list |
| 132 can change with the set of installed plug-ins on the user's machine, but Chrome | 132 can change with the set of installed plug-ins on the user's machine, but Chrome |
| 133 tries to keep the identifiers stable across plug-in updates. | 133 tries to keep the identifiers stable across plug-in updates. |
| 134 </p> | 134 </p> |
| 135 | 135 |
| 136 <h2 id="examples">Examples</h2> | 136 <h2 id="examples">Examples</h2> |
| 137 | 137 |
| 138 <p> | 138 <p> |
| 139 You can find samples of this API on the | 139 You can find samples of this API on the |
| 140 <a href="samples.html#contentSettings">sample page</a>. | 140 <a href="samples#contentSettings">sample page</a>. |
| 141 </p> | 141 </p> |
| OLD | NEW |