| OLD | NEW |
| 1 <p> | |
| 2 The content settings module allows you to change settings that control whether | |
| 3 websites can use features such as cookies, JavaScript, and plug-ins. | |
| 4 More generally speaking, content settings allow you to customize Chrome's | |
| 5 behavior on a per-site basis instead of globally.</p> | |
| 6 <p> | |
| 7 </p> | |
| 8 | |
| 9 <h2 id="manifest">Manifest</h2> | 1 <h2 id="manifest">Manifest</h2> |
| 10 <p>You must declare the "contentSettings" permission | 2 <p>You must declare the "contentSettings" permission |
| 11 in your extension's manifest to use the API. | 3 in your extension's manifest to use the API. |
| 12 For example:</p> | 4 For example:</p> |
| 13 <pre>{ | 5 <pre>{ |
| 14 "name": "My extension", | 6 "name": "My extension", |
| 15 ... | 7 ... |
| 16 <b>"permissions": [ | 8 <b>"permissions": [ |
| 17 "contentSettings" | 9 "contentSettings" |
| 18 ]</b>, | 10 ]</b>, |
| (...skipping 118 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 137 $ref:contentSettings.ContentSetting.getResourceIdentifiers method. The returned
list | 129 $ref:contentSettings.ContentSetting.getResourceIdentifiers method. The returned
list |
| 138 can change with the set of installed plug-ins on the user's machine, but Chrome | 130 can change with the set of installed plug-ins on the user's machine, but Chrome |
| 139 tries to keep the identifiers stable across plug-in updates. | 131 tries to keep the identifiers stable across plug-in updates. |
| 140 </p> | 132 </p> |
| 141 | 133 |
| 142 <h2 id="examples">Examples</h2> | 134 <h2 id="examples">Examples</h2> |
| 143 | 135 |
| 144 <p> | 136 <p> |
| 145 You can find samples of this API on the | 137 You can find samples of this API on the |
| 146 <a href="samples.html#contentSettings">sample page</a>. | 138 <a href="samples.html#contentSettings">sample page</a>. |
| 147 </p> | 139 </p> |
| OLD | NEW |