Upstream version 9.38.198.0

[platform/framework/web/crosswalk.git] / src / chrome / common / extensions / docs / templates / articles / permission_warnings.html

diff --git a/src/chrome/common/extensions/docs/templates/articles/permission_warnings.html b/src/chrome/common/extensions/docs/templates/articles/permission_warnings.html
index 78ff72a..513bdbe 100644 (file)
--- a/src/chrome/common/extensions/docs/templates/articles/permission_warnings.html
+++ b/src/chrome/common/extensions/docs/templates/articles/permission_warnings.html
@@ -100,12 +100,13 @@ brings up the following warning:
 
 <img src="{{static}}/images/perms-hw2.png"
   width="490" height="193"
-  alt="Permission warning: 'It can: Read and modify your data on api.flickr.com and flickr.com; Read and modify your browsing history'"
+  alt="Permission warning: 'It can: Read and modify your data on api.flickr.com; Access your browsing activity'"
   />
 
 
 <h2 id="warnings"> Warnings and their triggers </h2>
 
+{{^is_apps}}
 <p>
 It can be surprising when adding a permission such as "tabs"
 results in the seemingly unrelated warning
@@ -117,14 +118,7 @@ it can also be used to see the URL that's associated
 with every newly opened tab
 (using their $(ref:tabs.Tab) objects).
 </p>
-
-<p class="note">
-<b>Note:</b>
-As of Google Chrome 7,
-you no longer need to specify the "tabs" permission
-just to call <code>chrome.tabs.create()</code>
-or <code>chrome.tabs.update()</code>.
-</p>
+{{/is_apps}}
 
 <p>
 The following table lists the warning messages