chrome/common/extensions/docs/static/activeTab.html - Issue 10874057: Document the activeTab extension permission.

Side by Side Diff: chrome/common/extensions/docs/static/activeTab.html

Issue 10874057: Document the activeTab extension permission. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Created 8 years, 3 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

« no previous file with comments | « chrome/common/extensions/docs/server2/templates/public/extensions/activeTab.html ('k') | chrome/common/extensions/docs/static/manifest.html » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
(Empty)
	1 <div id="pageData-name" class="pageData">The activeTab permission</div>

	2

	3 <p>

	4 The <code>activeTab</code> permission is for extensions that perform an action o n a tab in response to the user. For example, an extension with a browser action that changes the formatting of the current page when clicked, or has a context menu which acts on the word that was clicked on.
	Aaron Boodman 2012/08/24 14:09:25 More direct: The _activeTab_ permission allows ex More direct: The _activeTab_ permission allows extensions to access the active tab in response to user gestures like clicking an extension button or context menu item. not at google - send to devlin 2012/08/27 04:45:50 Done. Show quoted text On 2012/08/24 14:09:25, Aaron Boodman wrote: > More direct: > > The _activeTab_ permission allows extensions to access the active tab in > response to user gestures like clicking an extension button or context menu > item. Done.
	5 </p>

	6

	7 <p>

	8 Traditionally such extensions would need to request both the <code><all_urls& gt;</code> permission and the <code>tabs</code> permission, requiring a scary in stall warning. With the <code>activeTab</code> permission, none of that is neces sary.
	Aaron Boodman 2012/08/24 14:09:25 Maybe you could turn this into a story/example: M Maybe you could turn this into a story/example: Many extensions only need access to a page in response to a user gesture on the extension. For example, consider a web clipping extension that has a browser action and context menu item. The extension doesn't need to run automatically on all pages, it only needs to run when one of its UI surfaces is acted upon. Without activeTab ... not at google - send to devlin 2012/08/27 04:45:50 Done. Show quoted text On 2012/08/24 14:09:25, Aaron Boodman wrote: > Maybe you could turn this into a story/example: > > Many extensions only need access to a page in response to a user gesture on the > extension. For example, consider a web clipping extension that has a browser > action and context menu item. The extension doesn't need to run automatically on > all pages, it only needs to run when one of its UI surfaces is acted upon. > > Without activeTab ... Done.
	9 </p>

	10

	11 </p>

	12 Formally, the <code>activeTab</code> permission allows an extension to use <a hr ef="tabs.html#method-executeScript">tabs.executeScript</a> and <a href="tabs.htm l#method-insertCSS">tabs.insertCSS</a> on any tab the extension has been invoked on, including any frames with the same security origin. The permission lasts un til the tab is navigated.

	13 </p>

	14

	15 <p>

	16 The following qualify as invocations:
	Aaron Boodman 2012/08/24 14:09:25 Since this is likely to rot, let's weaken it sligh Since this is likely to rot, let's weaken it slightly: The activeTab permission is activated whenever a piece of extension UI is acted upon by a user. At the time of writing, examples of such UI include: ... But this list will grow over time as more types of extension UI are added. not at google - send to devlin 2012/08/27 04:45:50 Done. Is it "extension UI are..." or "extension U Show quoted text On 2012/08/24 14:09:25, Aaron Boodman wrote: > Since this is likely to rot, let's weaken it slightly: > > The activeTab permission is activated whenever a piece of extension UI is acted > upon by a user. At the time of writing, examples of such UI include: > > ... > > But this list will grow over time as more types of extension UI are added. Done. Is it "extension UI are..." or "extension UIs are..."?
	17 <ul>

	18 <li>clicking on an extension’s browser action,

	19 <li>clicking on an extension’s page action,

	20 <li>clicking on an extension’s script badge,

	21 <li>accepting a suggestion from an extension’s omnibox,

	22 <li>invoking an action from an extension’s context menu, or

	23 <li>executing a command configured for an extension.

	24 </ul>

	25 </p>

OLD	NEW