diff options
Diffstat (limited to 'chrome/common/extensions/docs/templates/intros')
20 files changed, 69 insertions, 71 deletions
diff --git a/chrome/common/extensions/docs/templates/intros/bookmarks.html b/chrome/common/extensions/docs/templates/intros/bookmarks.html index 7ebe4f1..eafbd52 100644 --- a/chrome/common/extensions/docs/templates/intros/bookmarks.html +++ b/chrome/common/extensions/docs/templates/intros/bookmarks.html @@ -31,18 +31,18 @@ is either a bookmark or a folder (sometimes called a <em>group</em>). Each node in the tree is represented by a -<a href="#type-BookmarkTreeNode"><code>BookmarkTreeNode</code></a> object. +$ref:bookmarks.BookmarkTreeNode object. </p> <p> <code>BookmarkTreeNode</code> properties are used throughout the <code>chrome.bookmarks</code> API. For example, when you call -<a href="#method-create"><code>create()</code></a>, +$ref:bookmarks.create, you pass in the new node's parent (<code>parentId</code>), and, optionally, the node's <code>index</code>, <code>title</code>, and <code>url</code> properties. -See <a href="#type-BookmarkTreeNode"><code>BookmarkTreeNode</code></a> +See $ref:bookmarks.BookmarkTreeNode for information about the properties a node can have. </p> diff --git a/chrome/common/extensions/docs/templates/intros/browserAction.html b/chrome/common/extensions/docs/templates/intros/browserAction.html index 55460e7..2f1d1bd 100644 --- a/chrome/common/extensions/docs/templates/intros/browserAction.html +++ b/chrome/common/extensions/docs/templates/intros/browserAction.html @@ -96,7 +96,7 @@ and a <a href="#popups">popup</a>. <p>To set the icon, use the <b>default_icon</b> field of <b>browser_action</b> in the <a href="#manifest">manifest</a>, - or call the <a href="#method-setIcon">setIcon()</a> method. + or call the $ref:browserAction.setIcon method. </p> <p>To properly display icon when screen pixel density (ratio @@ -113,7 +113,7 @@ and a <a href="#popups">popup</a>. To set the tooltip, use the <b>default_title</b> field of <b>browser_action</b> in the <a href="#manifest">manifest</a>, -or call the <a href="#method-setTitle">setTitle()</a> method. +or call the $ref:browserAction.setTitle method. You can specify locale-specific strings for the <b>default_title</b> field; see <a href="i18n.html">Internationalization</a> for details. </p> @@ -132,8 +132,8 @@ see <a href="i18n.html">Internationalization</a> for details. <p> Set the text and color of the badge using -<a href="#method-setBadgeText">setBadgeText()</a> and -<a href="#method-setBadgeBackgroundColor">setBadgeBackgroundColor()</a>, +$ref:browserAction.setBadgeText and +$ref:browserAction.setBadgeBackgroundColor, respectively. </p> @@ -152,7 +152,7 @@ To add a popup to your browser action, create an HTML file with the popup's contents. Specify the HTML file in the <b>default_popup</b> field of <b>browser_action</b> in the <a href="#manifest">manifest</a>, or call the -<a href="#method-setPopup">setPopup()</a> method. +$ref:browserAction.setPopup method. </p> <h2 id="tips">Tips</h2> diff --git a/chrome/common/extensions/docs/templates/intros/contentSettings.html b/chrome/common/extensions/docs/templates/intros/contentSettings.html index 2353b15..06414f8 100644 --- a/chrome/common/extensions/docs/templates/intros/contentSettings.html +++ b/chrome/common/extensions/docs/templates/intros/contentSettings.html @@ -80,12 +80,12 @@ in the hostname.</li> <p> The URL taken into account when deciding which content setting to apply depends on the content type. For example, for -<a href="#property-notifications">notifications</a> settings are +$ref:contentSettings.notifications settings are based on the URL shown in the omnibox. This URL is called the "primary" URL.</p> <p> Some content types can take additional URLs into account. For example, whether a site is allowed to set a -<a href="#property-cookies">cookie</a> is decided based on the URL +$ref:contentSettings.cookies is decided based on the URL of the HTTP request (which is the primary URL in this case) as well as the URL shown in the omnibox (which is called the "secondary" URL). </p> @@ -120,7 +120,7 @@ is ordered by precedence:</p> <p> Resource identifiers allow you to specify content settings for specific subtypes of a content type. Currently, the only content type that supports -resource identifiers is <a href="#property-plugins"><code>plugins</code></a>, +resource identifiers is $ref:contentSettings.plugins, where a resource identifier identifies a specific plug-in. When applying content settings, first the settings for the specific plug-in are checked. If there are no settings found for the specific plug-in, the general content settings for @@ -134,8 +134,7 @@ it takes precedence over a rule without a resource identifier and the pattern </p> <p> You can get a list of resource identifiers for a content type by calling the -<a href="contentSettings.html#method-ContentSetting-getResourceIdentifiers"> -<code>getResourceIdentifiers()</code></a> method. The returned list +$ref:contentSettings.ContentSetting.getResourceIdentifiers method. The returned list can change with the set of installed plug-ins on the user's machine, but Chrome tries to keep the identifiers stable across plug-in updates. </p> diff --git a/chrome/common/extensions/docs/templates/intros/devtools_inspectedWindow.html b/chrome/common/extensions/docs/templates/intros/devtools_inspectedWindow.html index 30c4384..c1685ee 100644 --- a/chrome/common/extensions/docs/templates/intros/devtools_inspectedWindow.html +++ b/chrome/common/extensions/docs/templates/intros/devtools_inspectedWindow.html @@ -12,7 +12,7 @@ general introduction to using Developer Tools APIs. <h2 id="overview">Overview</h2> <p> -The <a href="#property-tabId"><code>tabId</code></a> property +The $ref:devtools.inspectedWindow.tabId property provides the tab identifier that you can use with the <a href="tabs.html"><code>chrome.tabs.*</code></a> API calls. However, please note that <code>chrome.tabs.*</code> API is not @@ -57,8 +57,7 @@ extension.</em> <p class="caution"> <strong>Important:</strong> Due to the security considerations explained above, the -<a href="tabs.html#method-executeScript"><code ->chrome.tabs.executeScript()</code></a> method is the preferred way for an +$ref:tabs.executeScript method is the preferred way for an extension to access DOM data of the inspected page in cases where the access to JavaScript state of the inspected page is not required.</em> </p><p> diff --git a/chrome/common/extensions/docs/templates/intros/devtools_panels.html b/chrome/common/extensions/docs/templates/intros/devtools_panels.html index 6de12cf..914368a 100644 --- a/chrome/common/extensions/docs/templates/intros/devtools_panels.html +++ b/chrome/common/extensions/docs/templates/intros/devtools_panels.html @@ -18,8 +18,8 @@ available to the pages within Developer Tools window, but you may invoke them by sending a request to the background page of your extension, similarly to how it's done in the <a href="overview.html#contentScripts">content scripts</a>. </p><p> -You can use the <code><a href="#method-setOpenResourceHandler" ->setOpenResourceHandler()</a></code> method to install a +You can use the <code>$ref:devtools.panels.setOpenResourceHandler +</code> method to install a callback function that handles user requests to open a resource (typically, a click on a resource link in the Developer Tools window). At most one of the installed handlers gets called; users can specify (using the Developer Tools diff --git a/chrome/common/extensions/docs/templates/intros/downloads.html b/chrome/common/extensions/docs/templates/intros/downloads.html index ee107d1..624d733 100644 --- a/chrome/common/extensions/docs/templates/intros/downloads.html +++ b/chrome/common/extensions/docs/templates/intros/downloads.html @@ -6,7 +6,7 @@ manipulate, and search for downloads.</p> <p> You must declare the 'downloads' permission in the <a href='manifest.html'>extension manifest</a> to use this API, along with <a href='manifest.html#permissions'>host permissions</a> for any hosts that you -may pass to <a href='#method-download'>download()</a>.</p> +may pass to $ref:downloads.download.</p> <pre>{ 'name': 'My extension', @@ -18,10 +18,10 @@ may pass to <a href='#method-download'>download()</a>.</p> ... }</pre> -<p>If the URL's hostname is not specified in the permissions, then <a -href='#method-download'>download()</a> will call its callback with a null -<code>downloadId</code> and set the <a -href='extension.html#property-lastError'>chrome.extensions.lastError</a> +<p>If the URL's hostname is not specified in the permissions, then +$ref:downloads.download will call its callback with a null +<code>downloadId</code> and set the +$ref:runtime.lastError object to indicate that the extension does not have permission to access that hostname.</p> diff --git a/chrome/common/extensions/docs/templates/intros/events.html b/chrome/common/extensions/docs/templates/intros/events.html index d40e231..c0fab99 100644 --- a/chrome/common/extensions/docs/templates/intros/events.html +++ b/chrome/common/extensions/docs/templates/intros/events.html @@ -25,9 +25,9 @@ is always a function that you define to handle the event, but the parameters to the function depend on which event you're handling. Checking the documentation for -<a href="tabs.html#event-onCreated"><code>chrome.tabs.onCreated</code></a>, +$ref:tabs.onCreated, you can see that the function has a single parameter: -a <a href="tabs.html#type-Tab">Tab</a> object +a $ref:tabs.Tab object that has details about the newly created tab. </p> @@ -84,9 +84,9 @@ var rule = { don't call a callback function when events happen but test whether any registered rule has at least one fulfilled condition and execute the actions associated with this rule. Event objects supporting the declarative API have -three relevant methods: <a href="#method-addRules"><code>addRules()</code></a>, -<a href="#method-removeRules"><code>removeRules()</code></a>, and -<a href="#method-getRules"><code>getRules()</code></a>. +three relevant methods: $ref:events.Event.addRules, +$ref:events.Event.removeRules, and +$ref:events.Event.getRules. </p> <h3 id="addingrules">Adding rules</h3> @@ -108,8 +108,8 @@ contains an array of inserted rules appearing in the same order as in the passed <code>rule_list</code> where the optional parameters <code>id</code> and <code>priority</code> were filled with the generated values. If any rule is invalid, e.g., because it contained an invalid condition or action, none of the -rules are added and the <a - href="extension.html#property-lastError">lastError</a> variable is set when +rules are added and the + $ref:runtime.lastError variable is set when the callback function is called. Each rule in <code>rule_list</code> must contain a unique identifier that is not currently used by another rule or an empty identifier. @@ -118,7 +118,7 @@ empty identifier. <p class="note"> <strong>Note:</strong> Rules are persistent across browsing sessions. Therefore, you should install rules during extension installation time using the -<code><a href="runtime.html#event-onInstalled">chrome.runtime.onInstalled</a></code> +<code>$ref:runtime.onInstalled</code> event. Note that this event is also triggered when an extension is updated. Therefore, you should first clear previously installed rules and then register new rules. @@ -204,8 +204,8 @@ of filters that an event supports will be listed in the documentation for that event in the "filters" section.</p> <p>When matching URLs (as in the example above), event filters support the same -URL matching capabilities as expressable with a <a - href="events.html#type-UrlFilter">UrlFilter</a>, except for scheme and port +URL matching capabilities as expressable with a + $ref:events.UrlFilter, except for scheme and port matching.</p> </div> diff --git a/chrome/common/extensions/docs/templates/intros/experimental_speechInput.html b/chrome/common/extensions/docs/templates/intros/experimental_speechInput.html index af6b8e9..9c9f994 100644 --- a/chrome/common/extensions/docs/templates/intros/experimental_speechInput.html +++ b/chrome/common/extensions/docs/templates/intros/experimental_speechInput.html @@ -49,7 +49,7 @@ chrome.experimental.speechInput.onResult.addListener(callback); </pre> <p>The <code>result</code> object contains an array of -<a href="#type-SpeechInputResultHypothesis">SpeechInputResultHypothesis</a> +$ref:experimental.speechInput.SpeechInputResultHypothesis sorted by decreasing likelihood.</p> <p>Recording automatically stops when results are received. It is safe to call diff --git a/chrome/common/extensions/docs/templates/intros/extension.html b/chrome/common/extensions/docs/templates/intros/extension.html index 2ab3f08..3dd97ba 100644 --- a/chrome/common/extensions/docs/templates/intros/extension.html +++ b/chrome/common/extensions/docs/templates/intros/extension.html @@ -17,21 +17,21 @@ can be used by content scripts: <dl> <dt> - <a href="#method-sendMessage"><code>sendMessage()</code></a> and - <a href="#event-onMessage"><code>onMessage</code></a> + $ref:extension.sendMessage and + $ref:extension.onMessage </dt> <dd> Simple communication with extension pages </dd> <dt> - <a href="#method-connect"><code>connect()</code></a> and - <a href="#event-onConnect"><code>onConnect</code></a> + $ref:extension.connect and + $ref:extension.onConnect </dt> <dd> Extended communication with extension pages </dd> <dt> - <a href="#method-getURL"><code>getURL()</code></a> + $ref:extension.getURL </dt> <dd> Access to extension resources such as image files diff --git a/chrome/common/extensions/docs/templates/intros/i18n.html b/chrome/common/extensions/docs/templates/intros/i18n.html index 4c0c2be..6be494c 100644 --- a/chrome/common/extensions/docs/templates/intros/i18n.html +++ b/chrome/common/extensions/docs/templates/intros/i18n.html @@ -546,7 +546,7 @@ status.innerText = chrome.i18n.getMessage("error", errorDetails); For more information about placeholders, see the <a href="i18n-messages.html">Locale-Specific Messages</a> page. For details on calling <code>getMessage()</code>, see the -<a href="#method-getMessage">API reference</a>. +$ref:[i18n.getMessage API reference]. </p> <h3 id="example-accept-languages">Example: getAcceptLanguages</h3> @@ -566,5 +566,5 @@ function getAcceptLanguages() { <p> For details on calling <code>getAcceptLanguages()</code>, see the -<a href="#method-getAcceptLanguages">API reference</a>. +$ref:[i18n.getAcceptLanguages API reference]. </p>
\ No newline at end of file diff --git a/chrome/common/extensions/docs/templates/intros/management.html b/chrome/common/extensions/docs/templates/intros/management.html index ae5076a..4319a8d 100644 --- a/chrome/common/extensions/docs/templates/intros/management.html +++ b/chrome/common/extensions/docs/templates/intros/management.html @@ -19,5 +19,5 @@ For example:</p> <p> The one method that doesn't require the "management" permission is -<a href="#method-getPermissionWarningsByManifest"><code>getPermissionWarningsByManifest</code></a> +$ref:management.getPermissionWarningsByManifest </p>
\ No newline at end of file diff --git a/chrome/common/extensions/docs/templates/intros/pageAction.html b/chrome/common/extensions/docs/templates/intros/pageAction.html index cc95f44..f6c0deb 100644 --- a/chrome/common/extensions/docs/templates/intros/pageAction.html +++ b/chrome/common/extensions/docs/templates/intros/pageAction.html @@ -80,8 +80,8 @@ by reading about the <p> You make a page action appear and disappear using the -<a href="#method-show">show()</a> and -<a href="#method-hide">hide()</a> methods, respectively. +$ref:pageAction.show and +$ref:pageAction.hide methods, respectively. By default, a page action is hidden. When you show it, you specify the tab in which the icon should appear. diff --git a/chrome/common/extensions/docs/templates/intros/proxy.html b/chrome/common/extensions/docs/templates/intros/proxy.html index 7a61dd0..81fa769 100644 --- a/chrome/common/extensions/docs/templates/intros/proxy.html +++ b/chrome/common/extensions/docs/templates/intros/proxy.html @@ -23,10 +23,10 @@ For example:</p> <p> Proxy settings are defined in a -<a href="#type-ProxyConfig"><code>ProxyConfig</code></a> object. Depending on +$ref:proxy.ProxyConfig object. Depending on Chrome's proxy settings, the settings may contain -<a href="#type-ProxyRules"><code>ProxyRules</code></a> or a <a - href="#type-PacScript"><code>PacScript</code></a>. +$ref:proxy.ProxyRules or a + $ref:proxy.PacScript. </p> <h3 id="proxy_modes">Proxy modes</h3> @@ -51,15 +51,15 @@ values: <dt><code>pac_script</code></dt> <dd>In <code>pac_script</code> mode the proxy configuration is determined by a PAC script that is either retrieved from the URL specified in the - <a href="#type-PacScript"><code>PacScript</code></a> object or + $ref:proxy.PacScript object or taken literally from the <code>data</code> element specified in the - <a href="#type-PacScript"><code>PacScript</code></a> object. + $ref:proxy.PacScript object. Besides this, this mode allows no further parameters in the <code>ProxyConfig</code> object.</dd> <dt><code>fixed_servers</code></dt> <dd>In <code>fixed_servers</code> mode the proxy configuration is codified in - a <a href="#type-ProxyRules><code>ProxyRules"><code>ProxyRules</code></a> + a $ref:proxy.ProxyRules object. Its structure is described in <a href="#proxy_rules">Proxy rules</a>. Besides this, the <code>fixed_servers</code> mode allows no further parameters in the <code>ProxyConfig</code> object.</dd> @@ -77,7 +77,7 @@ values: <h3 id="proxy_rules">Proxy rules</h3> <p> -The <a href="#type-ProxyRules"><code>ProxyRules</code></a> object can contain +The $ref:proxy.ProxyRules object can contain either a <code>singleProxy</code> attribute or a subset of <code>proxyForHttp</code>, <code>proxyForHttps</code>, <code>proxyForFtp</code>, and <code>fallbackProxy</code>. @@ -98,7 +98,7 @@ proxy server. <p> A proxy server is configured in a -<a href="#type-ProxyServer"><code>ProxyServer</code></a> object. The connection +$ref:proxy.ProxyServer object. The connection to the proxy server (defined by the <code>host</code> attribute) uses the protocol defined in the <code>scheme</code> attribute. If no <code>scheme</code> is specified, the proxy connection defaults to <code>http</code>. @@ -106,7 +106,7 @@ is specified, the proxy connection defaults to <code>http</code>. <p> If no <code>port</code> is defined in a -<a href="#type-ProxyServer"><code>ProxyServer</code></a> object, the port is +$ref:proxy.ProxyServer object, the port is derived from the scheme. The default ports are: <table> <tr><th>Scheme</th><th>Port</th></tr> diff --git a/chrome/common/extensions/docs/templates/intros/pushMessaging.html b/chrome/common/extensions/docs/templates/intros/pushMessaging.html index 5438009..19ca09d 100644 --- a/chrome/common/extensions/docs/templates/intros/pushMessaging.html +++ b/chrome/common/extensions/docs/templates/intros/pushMessaging.html @@ -226,7 +226,7 @@ Your app or extension will need to send this value to its application server so that the server can trigger push messages back. To get the user's channel ID, -call <a href="http://developer.chrome.com/apps/pushMessaging.html#method-getChannelId">getChannelId</a>. +call $ref:pushMessaging.getChannelId. Use the callback function to send the channel ID back to your app or extension. </p> @@ -450,7 +450,7 @@ your app or extension on the Extensions management page (go to <strong>chrome://extensions</strong> in your browser). Your app or extension doesn't need to be running, just installed. You will need to get the channel ID at install time -using <a href="app.runtime.html#event-onLaunched">chrome.app.runtime.onLaunched.addListener</a>. +using $ref:app.runtime.onLaunched. Then, use that channel ID on the server to send a test push message through the system. All going well, diff --git a/chrome/common/extensions/docs/templates/intros/tabs.html b/chrome/common/extensions/docs/templates/intros/tabs.html index 8002b16..88e750e 100644 --- a/chrome/common/extensions/docs/templates/intros/tabs.html +++ b/chrome/common/extensions/docs/templates/intros/tabs.html @@ -26,10 +26,10 @@ For example: }</pre> <p> -Three methods (<a href="#method-create"><code>create</code></a>, -<a href="#method-update"><code>update</code></a> and -<a href="#method-remove"><code>remove</code></a>) and one event -(<a href="#event-onRemoved"><code>onRemoved</code></a>) don't require the "tabs" +Three methods ($ref:tabs.create, +$ref:tabs.update and +$ref:tabs.remove) and one event +($ref:tabs.onRemoved) don't require the "tabs" permission. </p> diff --git a/chrome/common/extensions/docs/templates/intros/tts.html b/chrome/common/extensions/docs/templates/intros/tts.html index 93b88ac..46a00ea 100644 --- a/chrome/common/extensions/docs/templates/intros/tts.html +++ b/chrome/common/extensions/docs/templates/intros/tts.html @@ -55,13 +55,13 @@ chrome.tts.speak( </pre> <p>A complete description of all options can be found in the -<a href="#method-speak">speak() method documentation</a> below. +$ref:tts.speak below. Not all speech engines will support all options.</p> <p>To catch errors and make sure you're calling <code>speak()</code> correctly, pass a callback function that takes no arguments. Inside the callback, check -<a href="extension.html#property-lastError">chrome.extension.lastError</a> +$ref:runtime.lastError to see if there were any errors.</p> <pre>chrome.tts.speak( diff --git a/chrome/common/extensions/docs/templates/intros/ttsEngine.html b/chrome/common/extensions/docs/templates/intros/ttsEngine.html index 38febe7..a1e766e 100644 --- a/chrome/common/extensions/docs/templates/intros/ttsEngine.html +++ b/chrome/common/extensions/docs/templates/intros/ttsEngine.html @@ -15,8 +15,8 @@ to the calling function to report the status. <p>An extension can register itself as a speech engine. By doing so, it can intercept some or all calls to functions such as -<a href="tts.html#method-speak"><code>speak()</code></a> and -<a href="tts.html#method-stop"><code>stop()</code></a> +$ref:tts.speak and +$ref:tts.stop and provide an alternate implementation. Extensions are free to use any available web technology to provide speech, including streaming audio from a server, HTML5 audio, @@ -117,7 +117,7 @@ not sent by the speech engine; they are generated automatically by Chrome.</p> <p>Text-to-speech clients can get the voice information from your extension's manifest by calling -<a href="tts.html#method-getVoices">getVoices()</a>, +$ref:tts.getVoices, assuming you've registered speech event listeners as described below.</p> <h2 id="handling_speech_events">Handling speech events</h2> diff --git a/chrome/common/extensions/docs/templates/intros/types.html b/chrome/common/extensions/docs/templates/intros/types.html index c2cf8b4..67257dd 100644 --- a/chrome/common/extensions/docs/templates/intros/types.html +++ b/chrome/common/extensions/docs/templates/intros/types.html @@ -2,8 +2,8 @@ The <code>chrome.types</code> module contains type declarations for Chrome. Currently this comprises only a prototype for giving other modules access to manage Chrome browser settings. This prototype is used, -for example, for <a - href="proxy.html#property-settings"><code>chrome.proxy.settings</code></a>. +for example, for + $ref:proxy.settings. </p> <h2 id="ChromeSetting">Chrome settings</h2> diff --git a/chrome/common/extensions/docs/templates/intros/webRequest.html b/chrome/common/extensions/docs/templates/intros/webRequest.html index 9bbcb7f..8dc5ae0 100644 --- a/chrome/common/extensions/docs/templates/intros/webRequest.html +++ b/chrome/common/extensions/docs/templates/intros/webRequest.html @@ -183,15 +183,15 @@ depends on the specific event type as well as the content of <p>If the optional <code>opt_extraInfoSpec</code> array contains the string <code>'blocking'</code> (only allowed for specific events), the callback function is handled synchronously. That means that the request is blocked until -the callback function returns. In this case, the callback can return a <a - href="#type-BlockingResponse">BlockingResponse</a> that determines the further +the callback function returns. In this case, the callback can return a + $ref:webRequest.BlockingResponse that determines the further life cycle of the request. Depending on the context, this response allows cancelling or redirecting a request (<code>onBeforeRequest</code>), cancelling a request or modifying headers (<code>onBeforeSendHeaders</code>, <code>onHeadersReceived</code>), or providing authentication credentials (<code>onAuthRequired</code>).</p> -<p>The <a href="#type-RequestFilter">RequestFilter</a> +<p>The $ref:webRequest.RequestFilter <code>filter</code> allows limiting the requests for which events are triggered in various dimensions: <dl> @@ -202,7 +202,7 @@ triggered in various dimensions: <dd>Request types such as <code>main_frame</code> (a document that is loaded for a top-level frame), <code>sub_frame</code> (a document that is loaded for an embedded frame), and <code>image</code> (an image on a web site). - See <a href="#type-RequestFilter">RequestFilter</a>.</dd> + See $ref:webRequest.RequestFilter.</dd> <dt>Tab ID</dt> <dd>The identifier for one tab.</dd> <dt>Window ID</dt> diff --git a/chrome/common/extensions/docs/templates/intros/windows.html b/chrome/common/extensions/docs/templates/intros/windows.html index 2b38b65..87e1c1b 100644 --- a/chrome/common/extensions/docs/templates/intros/windows.html +++ b/chrome/common/extensions/docs/templates/intros/windows.html @@ -43,7 +43,7 @@ different from the topmost or focused window. creates a few tabs or windows from a single HTML file, and that the HTML file contains a call to -<a href="tabs.html#method-getSelected">chrome.tabs.getSelected</a>. +$ref:tabs.query. The current window is the window that contains the page that made the call, no matter what the topmost window is. </p> |