summaryrefslogtreecommitdiffstats
path: root/chrome/common/extensions/docs/static/permission_warnings.html
diff options
context:
space:
mode:
Diffstat (limited to 'chrome/common/extensions/docs/static/permission_warnings.html')
-rw-r--r--chrome/common/extensions/docs/static/permission_warnings.html28
1 files changed, 18 insertions, 10 deletions
diff --git a/chrome/common/extensions/docs/static/permission_warnings.html b/chrome/common/extensions/docs/static/permission_warnings.html
index 4671f58..b70280f 100644
--- a/chrome/common/extensions/docs/static/permission_warnings.html
+++ b/chrome/common/extensions/docs/static/permission_warnings.html
@@ -109,7 +109,7 @@ brings up the following warning:
<p>
It can be surprising when adding a permission such as "tabs"
results in the seemingly unrelated warning
-that the extension can access your browsing history.
+that the extension can access your browsing activity.
The reason for the warning is that
although the <code>chrome.tabs</code> API
might be used only to open new tabs,
@@ -174,22 +174,30 @@ that trigger them.
</td>
<td>
<!-- HasEffectiveBrowsingHistoryPermission -->
- "history" or "tabs" permission
+ "history" permission
</td>
<td>
<p>
- The "tabs" permission is required by the
- <a href="tabs.html"><code>chrome.tabs</code></a> and
- <a href="windows.html"><code>chrome.windows</code></a> modules.
- </p>
- <p>
The "history" permission is required by
<a href="history.html"><code>chrome.history</code></a>.
</p>
+ </td>
+</tr>
+
+<tr>
+ <td style="font-weight:bold">
+ <!-- IDS_EXTENSION_PROMPT_WARNING_TABS -->
+ Your tabs and browsing activity
+ </td>
+ <td>
+ <!-- HasEffectiveBrowsingHistoryPermission -->
+ "tabs" permission
+ </td>
+ <td>
<p>
- Adding "tabs" to an existing extension
- that already has "history", or vice versa,
- doesn't cause a warning when the extension is autoupdated.
+ The "tabs" permission is required by the
+ <a href="tabs.html"><code>chrome.tabs</code></a> and
+ <a href="windows.html"><code>chrome.windows</code></a> modules.
</p>
</td>
</tr>